You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Torsten Curdt <tc...@apache.org> on 2007/05/31 03:49:18 UTC
[vote] releasing jci RC3 as 1.0 ...maybe this time?
Only pom and license header changes since RC2. We are voting on the
actual binaries for the release.
http://jakarta.apache.org/commons/jci/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-core/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-fam/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-eclipse/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-groovy/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-janino/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-javac/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-rhino/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
apache/commons/commons-jci-examples/1.0/
Please cast you votes to release RC3.
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[result] [vote] releasing jci RC4 as 1.0
Posted by Torsten Curdt <tc...@apache.org>.
With the following votes the release of commons jci has passed:
+1 Oliver Heger
+1 Vadim Gritsenko
+1 Phil Steitz
+1 Torsten Curdt
no -1 votes
I will push out the artifacts tomorrow.
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Phil Steitz <ph...@gmail.com>.
+1
Builds happily, sigs and hashes are good and everything else looks good to me.
Thanks for rolling the source distro.
Phil
On 6/13/07, Torsten Curdt <tc...@apache.org> wrote:
> As (more or less) requested I've also created a source and binary
> distributions
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
>
> The website is live
>
> http://jakarta.apache.org/commons/jci/
>
> And maven artifacts are here
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-core/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-fam/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-eclipse/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-groovy/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-janino/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-javac/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-rhino/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-examples/1.0/
>
> So please cast your votes to release commons jci RC4 as 1.0
>
> cheers
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Oliver Heger <ol...@oliver-heger.de>.
Torsten Curdt wrote:
>
>
> What version of maven are you using? You did "mvn install"?
>
>> Why does it want to load a test jar?
>
> It is sharing code with the core.
>
> cheers
> --
> Torsten
Ah, I did a mvn package. With mvn install everything works fine. So here
is my +1.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Torsten Curdt <tc...@apache.org>.
On 14.06.2007, at 22:12, Oliver Heger wrote:
> Henri Yandell wrote:
>> Only negative I've found is that the distribution files unpack into
>> the current directory rather than a commons-jci-1.0 or a
>> commons-jci-1.0-src directory.
>> Once unpacked, the source does happily rebuild. KEYS are good - using
>> the BCEL one.
>> Hen
OK ...repackaged the same artifacts with proper dirs.
> I have made similar observations. However I have a problem with
> building from the sources. The build fails with the error message
> below. Any idea what could be the problem?
What version of maven are you using? You did "mvn install"?
> Why does it want to load a test jar?
It is sharing code with the core.
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Oliver Heger <ol...@oliver-heger.de>.
Henri Yandell wrote:
> Only negative I've found is that the distribution files unpack into
> the current directory rather than a commons-jci-1.0 or a
> commons-jci-1.0-src directory.
>
> Once unpacked, the source does happily rebuild. KEYS are good - using
> the BCEL one.
>
> Hen
I have made similar observations. However I have a problem with building
from the sources. The build fails with the error message below. Any idea
what could be the problem? Why does it want to load a test jar?
Oliver
[INFO] Building compiler-eclipse
[INFO] task-segment: [package]
[INFO]
----------------------------------------------------------------------------
Downloading:
http://repo1.maven.org/maven2/org/apache/commons/commons-jci-core/1.0/commons-jci-core-1.0-tests.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.commons:commons-jci-core:test-jar:tests:1.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.commons
-DartifactId=commons-jci-core \
-Dversion=1.0 -Dpackaging=test-jar -Dfile=/path/to/file
Path to dependency:
1) org.apache.commons:commons-jci-eclipse:jar:1.0
2) org.apache.commons:commons-jci-core:test-jar:tests:1.0
----------
1 required artifact is missing.
for artifact:
org.apache.commons:commons-jci-eclipse:jar:1.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository)
>
> On 6/13/07, Torsten Curdt <tc...@apache.org> wrote:
>> As (more or less) requested I've also created a source and binary
>> distributions
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
>>
>> The website is live
>>
>> http://jakarta.apache.org/commons/jci/
>>
>> And maven artifacts are here
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-core/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-fam/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-eclipse/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-groovy/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-janino/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-javac/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-rhino/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>> apache/commons/commons-jci-examples/1.0/
>>
>> So please cast your votes to release commons jci RC4 as 1.0
>>
>> cheers
>> --
>> Torsten
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Henri Yandell <fl...@gmail.com>.
Only negative I've found is that the distribution files unpack into
the current directory rather than a commons-jci-1.0 or a
commons-jci-1.0-src directory.
Once unpacked, the source does happily rebuild. KEYS are good - using
the BCEL one.
Hen
On 6/13/07, Torsten Curdt <tc...@apache.org> wrote:
> As (more or less) requested I've also created a source and binary
> distributions
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
>
> The website is live
>
> http://jakarta.apache.org/commons/jci/
>
> And maven artifacts are here
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-core/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-fam/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-eclipse/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-groovy/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-janino/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-javac/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-rhino/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-examples/1.0/
>
> So please cast your votes to release commons jci RC4 as 1.0
>
> cheers
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Torsten Curdt <tc...@apache.org>.
On 14.06.2007, at 20:18, sebb wrote:
> On 13/06/07, Torsten Curdt <tc...@apache.org> wrote:
>> As (more or less) requested I've also created a source and binary
>> distributions
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
>
> No KEYS file?
>
> There's one in SVN, but it will need to be in dist as well at some
> point.
No, it doesn't. None of the commons releases I checked include the
KEYS file. Just as for the other releases it will be linked to from
the download page.
>> The website is live
>>
>> http://jakarta.apache.org/commons/jci/
>
> No reference to KEYS file - or is that going to be done via
>
> http://jakarta.apache.org/site/downloads/downloads_commons-jci.cgi ?
Yes. Once it is on the mirrors I will also include a link to the
download on the website.
>> So please cast your votes to release commons jci RC4 as 1.0
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by sebb <se...@gmail.com>.
On 13/06/07, Torsten Curdt <tc...@apache.org> wrote:
> As (more or less) requested I've also created a source and binary
> distributions
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
No KEYS file?
There's one in SVN, but it will need to be in dist as well at some point.
> The website is live
>
> http://jakarta.apache.org/commons/jci/
No reference to KEYS file - or is that going to be done via
http://jakarta.apache.org/site/downloads/downloads_commons-jci.cgi ?
> And maven artifacts are here
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-core/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-fam/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-eclipse/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-groovy/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-janino/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-javac/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-rhino/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
> apache/commons/commons-jci-examples/1.0/
>
> So please cast your votes to release commons jci RC4 as 1.0
>
> cheers
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Torsten Curdt wrote:
>>>> As (more or less) requested I've also created a source and binary
>>>> distributions
>>>>
>>>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
>>
>> These look good, +1.
...
>> I found problem with missing LICENSE and NOTICE files in:
>> commons-jci-core-1.0-javadoc.jar
>> commons-jci-core-1.0-tests.jar
>> commons-jci-eclipse-1.0-javadoc.jar
>> commons-jci-examples-1.0-javadoc.jar
>> commons-jci-fam-1.0-javadoc.jar
>> commons-jci-groovy-1.0-javadoc.jar
>> commons-jci-janino-1.0-javadoc.jar
>> commons-jci-javac-1.0-javadoc.jar
>> commons-jci-rhino-1.0-javadoc.jar
>
> The files in those jars do include a license header in the package
> files. And I don't know of any (maven based) project including those two
> files explicitly inside those jars.
They are included in all the other files. Wouldn't it be trivial to add into
these files as well? It would be like couple of lines in ant... ;-)
> https://svn.apache.org/repos/asf/jakarta/commons/proper/jci/tags/1.0-RC4/core/src/main/java/org/apache/commons/jci/listeners/package.html
:)
>> License header is missing in files:
>> commons-jci-1.0-site.xml
>
> Seems like maven stripped the license:
> https://svn.apache.org/repos/asf/jakarta/commons/proper/jci/tags/1.0-RC4/src/site/site.xml
>
> But I personally don't see that as a blocker.
Probably not.
>> maven-metadata.xml (multiple files in different locations)
>
> This is only repository metadata generated by maven.
>
> So release like that?
Well definitely +1 for releasing tar.gz/zip files as they check out just fine;
but I don't know a thing about maven so I'm here in the dark - should those be
considered "release artifacts" or no? Shrug...
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Torsten Curdt <tc...@apache.org>.
>>> As (more or less) requested I've also created a source and binary
>>> distributions
>>>
>>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
>
> These look good, +1.
>
>
>>> And maven artifacts are here
>>>
>>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
>>> apache/commons/commons-jci/1.0/ http://people.apache.org/builds/
>>> jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-core/
>>> 1.0/ http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/
>>> org/apache/commons/commons-jci-fam/1.0/ http://people.apache.org/
>>> builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-
>>> eclipse/1.0/ http://people.apache.org/builds/jakarta-commons/jci/
>>> 1.0-RC4/org/apache/commons/commons-jci-groovy/1.0/ http://
>>> people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/
>>> commons/commons-jci-janino/1.0/ http://people.apache.org/builds/
>>> jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-javac/
>>> 1.0/ http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/
>>> org/apache/commons/commons-jci-rhino/1.0/ http://
>>> people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/
>>> commons/commons-jci-examples/1.0/
>
> I found problem with missing LICENSE and NOTICE files in:
> commons-jci-core-1.0-javadoc.jar
> commons-jci-core-1.0-tests.jar
> commons-jci-eclipse-1.0-javadoc.jar
> commons-jci-examples-1.0-javadoc.jar
> commons-jci-fam-1.0-javadoc.jar
> commons-jci-groovy-1.0-javadoc.jar
> commons-jci-janino-1.0-javadoc.jar
> commons-jci-javac-1.0-javadoc.jar
> commons-jci-rhino-1.0-javadoc.jar
The files in those jars do include a license header in the package
files. And I don't know of any (maven based) project including those
two files explicitly inside those jars.
https://svn.apache.org/repos/asf/jakarta/commons/proper/jci/tags/1.0-
RC4/core/src/main/java/org/apache/commons/jci/listeners/package.html
> License header is missing in files:
> commons-jci-1.0-site.xml
Seems like maven stripped the license:
https://svn.apache.org/repos/asf/jakarta/commons/proper/jci/tags/
1.0-RC4/src/site/site.xml
But I personally don't see that as a blocker.
> maven-metadata.xml (multiple files in different locations)
This is only repository metadata generated by maven.
So release like that?
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC4 as 1.0
Posted by Vadim Gritsenko <va...@reverycodes.com>.
>> From: Torsten Curdt <tc...@apache.org>
>> Date: 13. Juni 2007 21:06:37 MESZ
>> To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
>> Subject: [vote] releasing jci RC4 as 1.0
>>
>> As (more or less) requested I've also created a source and binary
>> distributions
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
These look good, +1.
>> And maven artifacts are here
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-core/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-fam/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-eclipse/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-groovy/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-janino/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-javac/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-rhino/1.0/
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/apache/commons/commons-jci-examples/1.0/
I found problem with missing LICENSE and NOTICE files in:
commons-jci-core-1.0-javadoc.jar
commons-jci-core-1.0-tests.jar
commons-jci-eclipse-1.0-javadoc.jar
commons-jci-examples-1.0-javadoc.jar
commons-jci-fam-1.0-javadoc.jar
commons-jci-groovy-1.0-javadoc.jar
commons-jci-janino-1.0-javadoc.jar
commons-jci-javac-1.0-javadoc.jar
commons-jci-rhino-1.0-javadoc.jar
License header is missing in files:
commons-jci-1.0-site.xml
maven-metadata.xml (multiple files in different locations)
So these can not be released as it is.
Vadim
>> So please cast your votes to release commons jci RC4 as 1.0
>>
>> cheers
>> --
>> Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[vote] releasing jci RC4 as 1.0
Posted by Torsten Curdt <tc...@apache.org>.
As (more or less) requested I've also created a source and binary
distributions
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
The website is live
http://jakarta.apache.org/commons/jci/
And maven artifacts are here
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-core/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-fam/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-eclipse/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-groovy/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-janino/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-javac/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-rhino/1.0/
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/org/
apache/commons/commons-jci-examples/1.0/
So please cast your votes to release commons jci RC4 as 1.0
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Oliver Heger <ol...@oliver-heger.de>.
Torsten Curdt wrote:
>
> On 02.06.2007, at 16:20, Oliver Heger wrote:
>
>> Torsten Curdt wrote:
>>> Votes ...someone?
>>> Should I provide a tgz so it's easier to grab?
>>> cheers
>>> -- Torsten
>>
>> I had a look at some of the jars, and they all look fine. But I am
>> wondering if you will provide source and binary distributions like the
>> other commons components do.
>
> IMO this would not make that much sense for jci as it is a multiproject.
> I doubt many people will need all compiler implementations. Actually I
> was thinking of releasing only via the maven repository sync.
>
>> These are the artifacts we typically vote on, so I am unsure how to
>> handle this case.
>
> Well I could run the assembly goal to create those distributions ...but
> who will use them?
>
> Don't know ...opinions?
>
> cheers
> --
> Torsten
Would it make sense to create distributions for the single modules? But
I assume, at least for the compiler implementations that will be overkill.
Well, for me it is fine the way it is. So I am +1 for the release.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
On 02.06.2007, at 16:20, Oliver Heger wrote:
> Torsten Curdt wrote:
>> Votes ...someone?
>> Should I provide a tgz so it's easier to grab?
>> cheers
>> --
>> Torsten
>
> I had a look at some of the jars, and they all look fine. But I am
> wondering if you will provide source and binary distributions like
> the other commons components do.
IMO this would not make that much sense for jci as it is a
multiproject. I doubt many people will need all compiler
implementations. Actually I was thinking of releasing only via the
maven repository sync.
> These are the artifacts we typically vote on, so I am unsure how to
> handle this case.
Well I could run the assembly goal to create those
distributions ...but who will use them?
Don't know ...opinions?
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Oliver Heger <ol...@oliver-heger.de>.
Torsten Curdt wrote:
> Votes ...someone?
>
> Should I provide a tgz so it's easier to grab?
>
> cheers
> --
> Torsten
I had a look at some of the jars, and they all look fine. But I am
wondering if you will provide source and binary distributions like the
other commons components do. These are the artifacts we typically vote
on, so I am unsure how to handle this case.
Oliver
>
> On 31.05.2007, at 03:49, Torsten Curdt wrote:
>
>> Only pom and license header changes since RC2. We are voting on the
>> actual binaries for the release.
>>
>> http://jakarta.apache.org/commons/jci/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-core/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-fam/1.0/
>>
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-eclipse/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-groovy/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-janino/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-javac/1.0/
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-rhino/1.0/
>>
>>
>> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/apache/commons/commons-jci-examples/1.0/
>>
>>
>> Please cast you votes to release RC3.
>>
>> cheers
>> --
>> Torsten
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Rahul Akolkar <ra...@gmail.com>.
On 6/2/07, Torsten Curdt <tc...@apache.org> wrote:
> Votes ...someone?
>
> Should I provide a tgz so it's easier to grab?
>
<snip/>
Not really for that purpose, but it would be good to have a complete
source assembly.
I'm not set to examine multi-module releases ATM. I've looked at these
in other releases (outside Commons) where they are few and far away
such that the overhead in showing due diligence and manually examining
each artifact seems affordable. We have talked about automated release
checkers (IIRC, you even mentioned you had some scripts) ... but I'm
not there yet.
Sorry for the aside, this being not pertinent to the vote in itself.
-Rahul
> cheers
> --
> Torsten
>
> On 31.05.2007, at 03:49, Torsten Curdt wrote:
>
> > Only pom and license header changes since RC2. We are voting on the
> > actual binaries for the release.
> >
> > http://jakarta.apache.org/commons/jci/
> >
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci/1.0/
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-core/1.0/
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-fam/1.0/
> >
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-eclipse/1.0/
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-groovy/1.0/
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-janino/1.0/
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-javac/1.0/
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-rhino/1.0/
> >
> > http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> > apache/commons/commons-jci-examples/1.0/
> >
> > Please cast you votes to release RC3.
> >
> > cheers
> > --
> > Torsten
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
Votes ...someone?
Should I provide a tgz so it's easier to grab?
cheers
--
Torsten
On 31.05.2007, at 03:49, Torsten Curdt wrote:
> Only pom and license header changes since RC2. We are voting on the
> actual binaries for the release.
>
> http://jakarta.apache.org/commons/jci/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-core/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-fam/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-eclipse/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-groovy/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-janino/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-javac/1.0/
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-rhino/1.0/
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC3/org/
> apache/commons/commons-jci-examples/1.0/
>
> Please cast you votes to release RC3.
>
> cheers
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by sebb <se...@gmail.com>.
On 14/06/07, Torsten Curdt <tc...@apache.org> wrote:
> >> > What would you think - how many percent of the developers that
> >> require
> >> > to build a project from the source have no http access to the
> >> internet?
> >> > Well, for jci I will personally send them a tar of the checkout
> >> - if
> >> > they have email :-p
> >
> > Source is not only needed for building the binary; it's also useful to
> > have access for debugging purposes in IDEs.
>
> Source artifact are in the maven repo for that exact reason.
But downloading stuff from the Maven repo is not as easy as getting it
from the Apache mirrors. Why should I have to get the binaries from
one place and the source from another completely different server?
> >> I would only advise to have a simple and classical way to
> >> distribute: an
> >> archive on a web server people can retrieve using a web browser.
>
> I the situation you are in it won't buy you anything as the build
> system is maven ...and it would need access to the network too.
Not necessarily; one can build up local copies of dependencies.
> How you get work done in such an environment is beyond me :)
Not my environment luckily.
> cheers
> --
> Torsten
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
>> > What would you think - how many percent of the developers that
>> require
>> > to build a project from the source have no http access to the
>> internet?
>> > Well, for jci I will personally send them a tar of the checkout
>> - if
>> > they have email :-p
>
> Source is not only needed for building the binary; it's also useful to
> have access for debugging purposes in IDEs.
Source artifact are in the maven repo for that exact reason.
>> I would only advise to have a simple and classical way to
>> distribute: an
>> archive on a web server people can retrieve using a web browser.
I the situation you are in it won't buy you anything as the build
system is maven ...and it would need access to the network too.
How you get work done in such an environment is beyond me :)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by sebb <se...@gmail.com>.
On 13/06/07, Luc Maisonobe <Lu...@free.fr> wrote:
> Torsten Curdt a écrit :
> >>> But seriously: be realistic. Those people building the releases from
> >>> will have subversion on their machine. And what can be simpler than a
> >>> one-liner to checkout the sources? Even downloading it from an apache
> >>> mirror is more work.
> >>
> >> People may have subversion but may not be able to use it.
> >>
> >> For example, I cannot use svn (nor cvs for that matter) through my
> >> corporate firewall.
> >
> > Wait a sec - you cannot use http from your development machine?
>
> http is fine from browsers that handle proxy with username/password,
> https was allowed only recently and may be shut down at any time, svn,
> ssh, cvs pserver are all filtered.
> Configuring svn clients to handle proxy username/password is not
> straightforward. For command-line svn it is handled by the user
> configuration file for servers, not by command-line options. I don't
> know about graphical clients or IDE embedded clients.
>
> I also know another company where http filtering is more strict, with
> files without any extension suppressed, files with some extensions
> suppressed, files modified on the fly to comply with some rules,
> user-agent is checked to allow only certified browsers to connect ...
> For example on this network, these so called « security rules »
> prevented me from downloading security upgrades for Debian computers
> (which are simple binary files downloads on an http server) ...
>
> >
> >> When I need a package that is only available by
> >> checking out from its repository, I have to check it out from home, put
> >> it on an USB stick and copy it the next day at work. It is very
> >> inconvenient.
> >
> > That's a truly sad story ...but we cannot provide a good solution for
> > every awkward workplace.
>
> I agree this is weird and cannot be generalized. I also agree that in
> the Apache case, this can be circumvented as anonymous access to the
> subversion server is http-based. I only wanted to point out that since a
> version control system is not a publication system, using it for that
> purpose may be tough for some people.
>
> > What would you think - how many percent of the developers that require
> > to build a project from the source have no http access to the internet?
> > Well, for jci I will personally send them a tar of the checkout - if
> > they have email :-p
Source is not only needed for building the binary; it's also useful to
have access for debugging purposes in IDEs.
> I would only advise to have a simple and classical way to distribute: an
> archive on a web server people can retrieve using a web browser.
+1
> Well, this is only my view and it is probably distorted, you can ignore it.
It's my view too.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Luc Maisonobe <Lu...@free.fr>.
Torsten Curdt a écrit :
>>> But seriously: be realistic. Those people building the releases from
>>> will have subversion on their machine. And what can be simpler than a
>>> one-liner to checkout the sources? Even downloading it from an apache
>>> mirror is more work.
>>
>> People may have subversion but may not be able to use it.
>>
>> For example, I cannot use svn (nor cvs for that matter) through my
>> corporate firewall.
>
> Wait a sec - you cannot use http from your development machine?
http is fine from browsers that handle proxy with username/password,
https was allowed only recently and may be shut down at any time, svn,
ssh, cvs pserver are all filtered.
Configuring svn clients to handle proxy username/password is not
straightforward. For command-line svn it is handled by the user
configuration file for servers, not by command-line options. I don't
know about graphical clients or IDE embedded clients.
I also know another company where http filtering is more strict, with
files without any extension suppressed, files with some extensions
suppressed, files modified on the fly to comply with some rules,
user-agent is checked to allow only certified browsers to connect ...
For example on this network, these so called « security rules »
prevented me from downloading security upgrades for Debian computers
(which are simple binary files downloads on an http server) ...
>
>> When I need a package that is only available by
>> checking out from its repository, I have to check it out from home, put
>> it on an USB stick and copy it the next day at work. It is very
>> inconvenient.
>
> That's a truly sad story ...but we cannot provide a good solution for
> every awkward workplace.
I agree this is weird and cannot be generalized. I also agree that in
the Apache case, this can be circumvented as anonymous access to the
subversion server is http-based. I only wanted to point out that since a
version control system is not a publication system, using it for that
purpose may be tough for some people.
> What would you think - how many percent of the developers that require
> to build a project from the source have no http access to the internet?
> Well, for jci I will personally send them a tar of the checkout - if
> they have email :-p
I would only advise to have a simple and classical way to distribute: an
archive on a web server people can retrieve using a web browser.
Well, this is only my view and it is probably distorted, you can ignore it.
regards,
Luc
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
>> But seriously: be realistic. Those people building the releases from
>> will have subversion on their machine. And what can be simpler than a
>> one-liner to checkout the sources? Even downloading it from an apache
>> mirror is more work.
>
> People may have subversion but may not be able to use it.
>
> For example, I cannot use svn (nor cvs for that matter) through my
> corporate firewall.
Wait a sec - you cannot use http from your development machine?
> When I need a package that is only available by
> checking out from its repository, I have to check it out from home,
> put
> it on an USB stick and copy it the next day at work. It is very
> inconvenient.
That's a truly sad story ...but we cannot provide a good solution for
every awkward workplace.
What would you think - how many percent of the developers that
require to build a project from the source have no http access to the
internet? Well, for jci I will personally send them a tar of the
checkout - if they have email :-p
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Luc Maisonobe <Lu...@free.fr>.
Torsten Curdt wrote:
>>> See above ...I think subversion is our source distribution. I don't
>>> really see a point in providing a classic source distribution. But
>>> maybe that's too much change for now ;)
>>
>> Yes, too much for me at least. In theory, voting on a tag and
>> pointing users there to get sources still could be viewed as a
>> release, but that is a big change from current practice and
>> inconvenient for users who prefer to build from release sources.
>
> It is a big change ...but who says that changes are bad? ;)
>
> But seriously: be realistic. Those people building the releases from
> will have subversion on their machine. And what can be simpler than a
> one-liner to checkout the sources? Even downloading it from an apache
> mirror is more work.
People may have subversion but may not be able to use it.
For example, I cannot use svn (nor cvs for that matter) through my
corporate firewall. When I need a package that is only available by
checking out from its repository, I have to check it out from home, put
it on an USB stick and copy it the next day at work. It is very
inconvenient.
Luc
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
>>> I'll prepare the assembly distributions and hope to get your +1
>>> then :)
>>>
>>
>> Of course! I just need to be able to build it first :)
>
> http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
Bah ...just found another problem. I rebuild and call a vote on RC4.
This is driving _me_ nuts!
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
>> So you are saying +1 for the assembly release ...but I don't get the
>> "who needs what" part.
>>
>
> What I meant was that I did not see it as a big user inconvenience to
> bundle all of the jars into a single release, since they are
> individually small. So, yes, I am +1 on putting together an assembly
> and making it available, along with the KEYS file, on the commons
> download page.
I just fear no one will use it ...but anyway.
>> See above ...I think subversion is our source distribution. I don't
>> really see a point in providing a classic source distribution. But
>> maybe that's too much change for now ;)
>
> Yes, too much for me at least. In theory, voting on a tag and
> pointing users there to get sources still could be viewed as a
> release, but that is a big change from current practice and
> inconvenient for users who prefer to build from release sources.
It is a big change ...but who says that changes are bad? ;)
But seriously: be realistic. Those people building the releases from
will have subversion on their machine. And what can be simpler than a
one-liner to checkout the sources? Even downloading it from an apache
mirror is more work.
> I think we should always distribute the source with our releases.
I think the only problem that I am seeing is that tags are not
immutable in svn. So in theory even a tag is not good enough but a
release is really a revision number.
> I guess what we are really talking about here is "what is a release?"
True. Especially with maven2 as the build system. I tried to raise
that a couple of times already. We need to come up with proper
release instructions for maven2 based projects. This is for sure.
<snip/>
>> I'll prepare the assembly distributions and hope to get your +1
>> then :)
>>
>
> Of course! I just need to be able to build it first :)
http://people.apache.org/builds/jakarta-commons/jci/1.0-RC4/dists/
Go nuts :)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Phil Steitz <ph...@gmail.com>.
On 6/4/07, Torsten Curdt <tc...@apache.org> wrote:
>
> On 04.06.2007, at 06:49, Phil Steitz wrote:
>
> > Sigs and hashes check fine, but I had to grab your key from
> > http://www.apache.org/dist/jakarta/bcel/KEYS. Make sure to add this
> > under JCI somewhere (see below)
>
> It's there
>
> http://svn.apache.org/repos/asf/jakarta/commons/proper/jci/tags/1.0-
> RC3/KEYS.txt
>
> > * I think that for consistency and at least to provide a definitive
> > location for the release artifacts, KEYS, and release notes, we should
> > continue the practice of rolling combined zips/tarballs and putting
> > these on the mirrors under /dist/jakarta-commons. The separate jars
> > in [cli] are pretty small, so the "who needs what" issue is not really
> > a big one here, IMO.
>
> So you are saying +1 for the assembly release ...but I don't get the
> "who needs what" part.
>
What I meant was that I did not see it as a big user inconvenience to
bundle all of the jars into a single release, since they are
individually small. So, yes, I am +1 on putting together an assembly
and making it available, along with the KEYS file, on the commons
download page.
> > ** It is not clear to me how to build the binaries from the provided
> > sources. The *sources* jars contain java source code. Do I need to
> > unpack this code with a common root and use the pom in
> > /org/apache/commons/commons-jci/1.0/commons-jci-1.0.pom? I think we
> > should provide either a conventional source distribution or some
> > instructions on how to unpack and build the sources
>
> Hm... I don't see the source jars to be used for building the whole
> project but provide the sources for things like debugging.
> So if you want to build it from the source I would expect people to
> check it out of subversion. Anyone that is capable of building a
> project should be able to do a svn checkout to get the source for that.
>
ASF releases need to include source. (See
http://www.apache.org/dev/release.html#what.) Admittedly, publishing
jars to a maven repo puts us into a grey area. I am not comfortable
going into that area though without a voted, full source,
validated-to-build release that the secondarily published artifacts
are part of.
> > * by itself is not a showstopper for me, but ** is. I think a basic
> > requirement that we have is that release binaries can be built from
> > the sources in our distributions. In the m1 days, we used to say
> > "maven clean dist" or at least "ant clean dist" needs to work from the
> > unpacked source distribution. I don't care if it is a shell script,
> > ant, maven, or provided instructions, but users should have an obvious
> > and effective way to build from the sources in our releases. Sorry if
> > I am just missing the obvious way to do this using m2.
>
> See above ...I think subversion is our source distribution. I don't
> really see a point in providing a classic source distribution. But
> maybe that's too much change for now ;)
Yes, too much for me at least. In theory, voting on a tag and
pointing users there to get sources still could be viewed as a
release, but that is a big change from current practice and
inconvenient for users who prefer to build from release sources. I
think we should always distribute the source with our releases.
I guess what we are really talking about here is "what is a release?"
and the link above is the only ASF definition that I can find. Could
be I will come around to seeing it as OK one day to just push binaries
+ source jars to repos (after voting on these artifacts *plus* svn
tags) and direct those who want to build from source to the tags, but
I am just not there yet. Still seems to me that as part of the
release, we should roll (and eventually archive) an actual buildable
source distro.
>
> I'll prepare the assembly distributions and hope to get your +1 then :)
>
Of course! I just need to be able to build it first :)
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Torsten Curdt <tc...@apache.org>.
On 04.06.2007, at 06:49, Phil Steitz wrote:
> Sigs and hashes check fine, but I had to grab your key from
> http://www.apache.org/dist/jakarta/bcel/KEYS. Make sure to add this
> under JCI somewhere (see below)
It's there
http://svn.apache.org/repos/asf/jakarta/commons/proper/jci/tags/1.0-
RC3/KEYS.txt
> * I think that for consistency and at least to provide a definitive
> location for the release artifacts, KEYS, and release notes, we should
> continue the practice of rolling combined zips/tarballs and putting
> these on the mirrors under /dist/jakarta-commons. The separate jars
> in [cli] are pretty small, so the "who needs what" issue is not really
> a big one here, IMO.
So you are saying +1 for the assembly release ...but I don't get the
"who needs what" part.
> ** It is not clear to me how to build the binaries from the provided
> sources. The *sources* jars contain java source code. Do I need to
> unpack this code with a common root and use the pom in
> /org/apache/commons/commons-jci/1.0/commons-jci-1.0.pom? I think we
> should provide either a conventional source distribution or some
> instructions on how to unpack and build the sources
Hm... I don't see the source jars to be used for building the whole
project but provide the sources for things like debugging.
So if you want to build it from the source I would expect people to
check it out of subversion. Anyone that is capable of building a
project should be able to do a svn checkout to get the source for that.
> * by itself is not a showstopper for me, but ** is. I think a basic
> requirement that we have is that release binaries can be built from
> the sources in our distributions. In the m1 days, we used to say
> "maven clean dist" or at least "ant clean dist" needs to work from the
> unpacked source distribution. I don't care if it is a shell script,
> ant, maven, or provided instructions, but users should have an obvious
> and effective way to build from the sources in our releases. Sorry if
> I am just missing the obvious way to do this using m2.
See above ...I think subversion is our source distribution. I don't
really see a point in providing a classic source distribution. But
maybe that's too much change for now ;)
I'll prepare the assembly distributions and hope to get your +1 then :)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
Posted by Phil Steitz <ph...@gmail.com>.
Sigs and hashes check fine, but I had to grab your key from
http://www.apache.org/dist/jakarta/bcel/KEYS. Make sure to add this
under JCI somewhere (see below)
* I think that for consistency and at least to provide a definitive
location for the release artifacts, KEYS, and release notes, we should
continue the practice of rolling combined zips/tarballs and putting
these on the mirrors under /dist/jakarta-commons. The separate jars
in [cli] are pretty small, so the "who needs what" issue is not really
a big one here, IMO.
** It is not clear to me how to build the binaries from the provided
sources. The *sources* jars contain java source code. Do I need to
unpack this code with a common root and use the pom in
/org/apache/commons/commons-jci/1.0/commons-jci-1.0.pom? I think we
should provide either a conventional source distribution or some
instructions on how to unpack and build the sources
* by itself is not a showstopper for me, but ** is. I think a basic
requirement that we have is that release binaries can be built from
the sources in our distributions. In the m1 days, we used to say
"maven clean dist" or at least "ant clean dist" needs to work from the
unpacked source distribution. I don't care if it is a shell script,
ant, maven, or provided instructions, but users should have an obvious
and effective way to build from the sources in our releases. Sorry if
I am just missing the obvious way to do this using m2.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org