Hi Karl,
we can simply need to revert the changes just before the 0.8.0-incubator
release.
When upgrading the ACE build to use Maven, firstly, we used the tags scm
with Maven sub-modules.
So I'm quite sure that reverting just before the 0.8.0-incubator, I can
prepare that for the next ACE release.
Regards
JB
On 11/17/2011 04:14 PM, Karl Pauls wrote:
Again, I'm not against doing things differently for future release
(and the reason this release looks like it does is because that is
configured like this in the apache-parent iirc). However, I'm still
confused what all of this has to do with the graduation proposal vote
and why this has to be on general@.
The release vote has passed a while ago and I don't see that the
release is invalid because we don't use a certain svn layout or maven
config. The source is in dist and the tags are in svn. I suggest we
move discussion about future release layouts to the ace-dev list and
into a separate thread unless you disagree.
regards,
Karl
On Thu, Nov 17, 2011 at 4:09 PM, sebb<seb...@gmail.com> wrote:
On 17 November 2011 14:07, Karl Pauls<karlpa...@gmail.com> wrote:
$ mkdir org.apache.ace.client.automation-0.8.0-incubator
$ cd org.apache.ace.client.automation-0.8.0-incubator/
$ wget
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar
s/source/sources/
$ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar
$ wget
http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom
$ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml
$ mvn clean install
=========================
Not exactly trivial compared with
$ svn co
http://svn.apache.org/repos/asf/incubator/ace/releases/org.apache.ace.client.automation-0.8.0-incubator
-- or --
$ unzip org.apache.ace.client.automation-0.8.0-incubator-source.zip
(if it existed)
and then
$ cd org.apache.ace.client.automation-0.8.0-incubator
$ mvn clean install
There's another (bigger) problem with the existing -sources.jar files.
They don't contain any unit tests, as far as I can tell, yet there are
some unit tests in SVN.
Surely the unit tests should be distributed as part of the source release?
==
This is quite easy to fix, just (vote on and) release zip/tar.gz
archives of the tags for each component.
I would drop the -sources.jar files from /dist as they aren't all that
useful for non-Maven downloads.
==
To make it easier to navigate the dist/ directory, may I suggest
creating binaries/ and source/ folders?
The source/ folder would contain all the current source zips/tgz archives
The binaries folders would contain binary jars and javadoc jars
The *.pom files would be removed, as the pom.xml files would be in the
appropriate source/ archive.
regards,
Karl
On Thu, Nov 17, 2011 at 2:54 PM, ant elder<ant.el...@gmail.com> wrote:
To try that I just went to the ACE downloads page which has a bunch of
jars and source jars to download, i downloaded the source of the first
one, org.apache.ace.client.automation-0.8.0-incubator-sources.jar, and
looking inside there is the source to some Java classes but no build
scripts or pom.xml file, so how would I go about building this?
...ant
On Thu, Nov 17, 2011 at 1:35 PM, Karl Pauls<karlpa...@gmail.com> wrote:
Again, we had this discussion before namely, when the actual release
vote happened. I'm still confused why we have to go through this
again. You should be able to build all of the components by using the
-source.jar's that are provided. They contain what is necessary i.e.,
the full source.
regards,
Karl
On Thu, Nov 17, 2011 at 2:30 PM, sebb<seb...@gmail.com> wrote:
On 17 November 2011 12:29, Karl Pauls<karlpa...@gmail.com> wrote:
I'm not sure what this has to do with the graduation vote. The release
as such has been accepted by the incubator pmc and there only need to
be one release. The source for each artifact is there, it is just per
artifact in the -source.jar.
AFAICT the full source (as in SVN trunk) is not actually present in
the distribution directory.
For example, where are the top-level files in SVN (BUILDING, README) ?
And the etc/ directory?
If I wanted to build any or all of the components, there does not
appear to be a way to do this from the files in the distribution.
There might be different set-up then a lot of other projects have it
but we release our stuff on a per artifact basis how it is done by for
example Apache Felix as well and never has been an issue (and didn't
become unmanageably either - also ymmv).
The ASF primarily releases source; releases must include full source.
I agree about the KEYS file. We should have uploaded it to the dist
dir as well but at least we have it at some place so it should be easy
to fix.
regards,
Karl
On Thu, Nov 17, 2011 at 1:07 PM, sebb<seb...@gmail.com> wrote:
On 17 November 2011 10:42, Marcel Offermans<marcel.offerm...@luminis.nl> wrote:
In my opinion, ACE is ready to begin the process of graduating from the Apache
Incubator to a Top Level Project.
Since joining the incubator in in May 2009 we've added 4 new committers (12 in
total now) from diverse organizations and did a release in May this year to
demonstrate we follow the Apache guidelines. We've shown an ability to
self-govern using accepted Apache practices and ACE continues to attract new
contributors and users.
The first step is to vote as a community, demonstrating that ACE is ready and
willing to graduate. Once this vote is succesful we create a board resolution
proposal or Charter and start a vote on the general incubator list. The full
process is described at
http://incubator.apache.org/guides/graduation.html#toplevel
The vote is open for at least 72 hours.
The last (and only) release was 0.8, as far as I can tell.
There is no KEYS file in http://www.apache.org/dist/incubator/ace/,
and there does not appear to be a full source archive of the project
anywhere.
The download page does not have a link to any source archives as far
as I can tell.
It does link to KEYS in SVN, but almost all other ASF projects have a
copy of KEYS in the appropriate /dist directory.
Normally releases are divided into binaries/ and source/ directories,
with a KEYS file in the top-level, i.e.
/dist/incubator/ace
- KEYS
- binaries/ace ....zip
- sources/ace....zip
Most of the files in the /dist/incubator/ace directory appear to be
Maven artifacts; normally these are not stored in /dist but only in
the Maven repo.
Indeed most of the files are also in Maven Central. The only non-Maven
files appear to be
org.apache.ace.target.devgateway-0.8.0-incubator-distribution.zip
org.apache.ace.target.devserver-0.8.0-incubator-distribution.zip
neither of which contains the source.
I would expect the above zips to be in
/dist/incubator/ace/binaries
with corresponding source files in
/dist/incubator/ace/source
The SVN layout [1] is also a bit unusual.
There is no tags/ directory for release tags, although there is a
releases/ directory containing individual entries for each release for
each component.
This is likely to become unmanageable very quickly, if every release
adds another 63 directory entries under releases/
[1] https://svn.apache.org/repos/asf/incubator/ace/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Karl Pauls
karlpa...@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
