You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Oliver Heger <ol...@oliver-heger.de> on 2007/11/01 16:04:29 UTC
[VOTE] Release Commons Configuration 1.5 based on RC1
The 1.5 release of Commons Configuration is overdue.
I have prepared a first release candidate. All artifacts including a
clirr report and the release notes can be found at
http://people.apache.org/~oheger/commons-configuration-1.5rc1/
The site is also available under
http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
Please take the time to have a look at the artifacts and cast your vote.
I will count the votes not before next Thursday (Nov. 8th).
Thanks.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Michiel Kalkman wrote:
> Just a minor, minor remark: the links in the changes don't seem to
> work. E.g. http://issues.apache.org/jira/browse/ViewIssue.jspa?key=CONFIGURATION-168.
> Should be http://issues.apache.org/jira/browse/CONFIGURATION-168.
>
> Regards,
> Michiel
Good catch. This was caused by an old version of the maven changes
plugin. With a newer version the links are correct, and so will be the
final site.
Thanks
Oliver
>
> On 11/1/07, Oliver Heger <ol...@oliver-heger.de> wrote:
>
>>The 1.5 release of Commons Configuration is overdue.
>>
>>I have prepared a first release candidate. All artifacts including a
>>clirr report and the release notes can be found at
>>http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>>
>>The site is also available under
>>http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>>
>>Please take the time to have a look at the artifacts and cast your vote.
>>I will count the votes not before next Thursday (Nov. 8th).
>>
>>Thanks.
>>Oliver
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Michiel Kalkman <mi...@gmail.com>.
Just a minor, minor remark: the links in the changes don't seem to
work. E.g. http://issues.apache.org/jira/browse/ViewIssue.jspa?key=CONFIGURATION-168.
Should be http://issues.apache.org/jira/browse/CONFIGURATION-168.
Regards,
Michiel
On 11/1/07, Oliver Heger <ol...@oliver-heger.de> wrote:
> The 1.5 release of Commons Configuration is overdue.
>
> I have prepared a first release candidate. All artifacts including a
> clirr report and the release notes can be found at
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>
> The site is also available under
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>
> Please take the time to have a look at the artifacts and cast your vote.
> I will count the votes not before next Thursday (Nov. 8th).
>
> Thanks.
> Oliver
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Jörg Schaible wrote:
> Hi Oliver,
>
> Oliver Heger wrote:
>
>> Jörg Schaible wrote:
> [snip]
>>> I can do this if you want, but I did not want to do any changes now while
>>> you're in the process of the release.
>>>
>>> - Jörg
>>>
>> As you probably have noticed, I am not that familiar with the whole
>> dependency stuff, so any help would be much appreciated. Just go ahead
>> and apply the necessary changes.
>
> Done. I was unsure about the build.xml though. It still references the old
> deps and generates a javadoc title for "Common Configurations 1.1-dev
> API" ;-)
>
> It was generated once with M1, but if I recreate it, a lot of variable
> substitutions are missing. Since I don't know how the policy is about that
> one, I leave it alone - maybe someone else can comment on it.
>
> - Jörg
>
Yes, this file was once generated and then manually adapted to our
specific location of the test files (the maven-ant-plugin did not take
the conf directory into account). If now dependencies are changed, the
file has to be updated, too.
I synced it with your changes and also fixed the title for the javadocs.
Thanks
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Oliver,
Oliver Heger wrote:
> Jörg Schaible wrote:
[snip]
>>
>> I can do this if you want, but I did not want to do any changes now while
>> you're in the process of the release.
>>
>> - Jörg
>>
> As you probably have noticed, I am not that familiar with the whole
> dependency stuff, so any help would be much appreciated. Just go ahead
> and apply the necessary changes.
Done. I was unsure about the build.xml though. It still references the old
deps and generates a javadoc title for "Common Configurations 1.1-dev
API" ;-)
It was generated once with M1, but if I recreate it, a lot of variable
substitutions are missing. Since I don't know how the policy is about that
one, I leave it alone - maybe someone else can comment on it.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Jörg Schaible wrote:
> Oliver Heger wrote:
>>> The only difference running the tests with Maven now is that
>>> exception's stack trace is printed to the screen instead of written
>>> into a log file (because of the now missing log4j dependency).
>>>
>> Ok, I will apply this patch to pom.xml. What about the maven 1 build?
>> Should it be tweaked, too?
>
> That's less critical, because the deps are not transitive. However, as Nicolas stated, it refers servletapi with the old groupId and also an ols xerces implementation. That should be synchronized with the M2 POM. You may add additionally log4j with test scope (and can therefore omit its exclusion in the ACL dep), then the output building ACC with M2 is as nice as before.
>
> I can do this if you want, but I did not want to do any changes now while you're in the process of the release.
>
> - Jörg
>
As you probably have noticed, I am not that familiar with the whole
dependency stuff, so any help would be much appreciated. Just go ahead
and apply the necessary changes.
TIA
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
Oliver Heger wrote:
>> The only difference running the tests with Maven now is that
>> exception's stack trace is printed to the screen instead of written
>> into a log file (because of the now missing log4j dependency).
>>
>
> Ok, I will apply this patch to pom.xml. What about the maven 1 build?
> Should it be tweaked, too?
That's less critical, because the deps are not transitive. However, as Nicolas stated, it refers servletapi with the old groupId and also an ols xerces implementation. That should be synchronized with the M2 POM. You may add additionally log4j with test scope (and can therefore omit its exclusion in the ACL dep), then the output building ACC with M2 is as nice as before.
I can do this if you want, but I did not want to do any changes now while you're in the process of the release.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Jörg Schaible wrote:
<snip/>
>
> xerces:xerces should be excluded, since JCC refers newer artifacts of xerces
> (with different groupId)
> ant-optional possibly also, unfortunately this artifact not even exists in
> 1.6.x series since it has been splitted.
>
> Current deps:
>
> joehni@paddy ~/java/commons-configuration-1.5-src $ mvn info:deps-test
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'info'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Commons Configuration
> [INFO] task-segment: [info:deps-test]
> [INFO] ----------------------------------------------------------------------------
> [WARNING] POM for 'commons-codec:commons-codec:pom:1.3:compile' is invalid.
> It will be ignored for artifact resolution. Reason: Failed to validate POM
> [WARNING]
> Artifact xml-apis:xml-apis:jar:1.0.b2:provided retains local
> scope 'provided' overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or remove the
> local scope.
>
> [WARNING]
> Artifact junit:junit:jar:3.8.1:test retains local scope 'test'
> overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or remove the
> local scope.
>
> [INFO] [info:deps-test]
> [INFO] commons-configuration:commons-configuration:jar:1.5
> [INFO] commons-collections:commons-collections:jar:3.2
> [INFO] mockobjects:mockobjects-jdk1.4-j2ee1.3:jar:0.09
> [INFO] dbunit:dbunit:jar:2.1
> [INFO] commons-lang:commons-lang:jar:2.3
> [INFO] junit-addons:junit-addons:jar:1.4
> [INFO] : xerces:xmlParserAPIs:jar:2.6.2
> [INFO] ant:ant:jar:1.6.5
> [INFO] commons-jxpath:commons-jxpath:jar:1.2
> [INFO] : xerces:xerces:jar:1.2.3
> [INFO] : ant:ant-optional:jar:1.5.1
> [INFO] : jdom:jdom:jar:b9
> [INFO] commons-digester:commons-digester:jar:1.8
> [INFO] : commons-logging:commons-logging:jar:1.1
> [INFO] : logkit:logkit:jar:1.0.1
> [INFO] : log4j:log4j:jar:1.2.12
> [INFO] : avalon-framework:avalon-framework:jar:4.1.3
> [INFO] javax.mail:mail:jar:1.4
> [INFO] : javax.activation:activation:jar:1.1
> [INFO] xml-apis:xml-apis:jar:1.0.b2
> [INFO] junit:junit:jar:3.8.1
> [INFO] javax.servlet:servlet-api:jar:2.4
> [INFO] commons-logging:commons-logging-api:jar:1.0.4
> [INFO] xerces:xercesImpl:jar:2.3.0
> [INFO] commons-pool:commons-pool:jar:1.1
> [INFO] commons-beanutils:commons-beanutils:jar:1.7.0
> [INFO] mockobjects:mockobjects-core:jar:0.09
> [INFO] commons-codec:commons-codec:jar:1.3
> [INFO] hsqldb:hsqldb:jar:1.7.2.2
> [INFO] xalan:xalan:jar:2.7.0
> [INFO] commons-dbcp:commons-dbcp:jar:1.2.2
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
>
>
> Applying this patch:
>
> ==================== %< ================
> joehni@paddy ~/java/commons-configuration-1.5-src $ diff -u pom.xml pom.new
> --- pom.xml 2007-11-01 15:13:40.000000000 +0100
> +++ pom.new 2007-11-05 22:12:41.546284773 +0100
> @@ -202,8 +202,23 @@
>
> <dependency>
> <groupId>commons-logging</groupId>
> - <artifactId>commons-logging-api</artifactId>
> - <version>1.0.4</version>
> + <artifactId>commons-logging</artifactId>
> + <version>1.1</version>
> + <!-- remove exclusions for JCL 1.1.1 -->
> + <exclusions>
> + <exclusion>
> + <groupId>logkit</groupId>
> + <artifactId>logkit</artifactId>
> + </exclusion>
> + <exclusion>
> + <groupId>log4j</groupId>
> + <artifactId>log4j</artifactId>
> + </exclusion>
> + <exclusion>
> + <groupId>avalon-framework</groupId>
> + <artifactId>avalon-framework</artifactId>
> + </exclusion>
> + </exclusions>
> </dependency>
>
> <dependency>
> @@ -230,6 +245,16 @@
> <artifactId>commons-jxpath</artifactId>
> <version>1.2</version>
> <optional>true</optional>
> + <exclusions>
> + <exclusion>
> + <groupId>xerces</groupId>
> + <artifactId>xerces</artifactId>
> + </exclusion>
> + <exclusion>
> + <groupId>ant</groupId>
> + <artifactId>ant-optional</artifactId>
> + </exclusion>
> + </exclusions>
> </dependency>
>
> <dependency>
> @@ -311,6 +336,12 @@
> <artifactId>junit-addons</artifactId>
> <version>1.4</version>
> <scope>test</scope>
> + <exclusions>
> + <exclusion>
> + <groupId>xerces</groupId>
> + <artifactId>xmlParserAPIs</artifactId>
> + </exclusion>
> + </exclusions>
> </dependency>
>
> <dependency>
> ==================== %< ================
>
> You end up with this deps:
>
> joehni@paddy ~/java/commons-configuration-1.5-src $ mvn -f pom.new
> info:deps-test
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'info'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Commons Configuration
> [INFO] task-segment: [info:deps-test]
> [INFO] ----------------------------------------------------------------------------
> [WARNING] POM for 'commons-codec:commons-codec:pom:1.3:compile' is invalid.
> It will be ignored for artifact resolution. Reason: Failed to validate POM
> [WARNING]
> Artifact xml-apis:xml-apis:jar:1.0.b2:provided retains local
> scope 'provided' overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or remove the
> local scope.
>
> [WARNING]
> Artifact junit:junit:jar:3.8.1:test retains local scope 'test'
> overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or remove the
> local scope.
>
> [INFO] [info:deps-test]
> [INFO] commons-configuration:commons-configuration:jar:1.5
> [INFO] commons-collections:commons-collections:jar:3.2
> [INFO] mockobjects:mockobjects-jdk1.4-j2ee1.3:jar:0.09
> [INFO] dbunit:dbunit:jar:2.1
> [INFO] commons-lang:commons-lang:jar:2.3
> [INFO] junit-addons:junit-addons:jar:1.4
> [INFO] commons-jxpath:commons-jxpath:jar:1.2
> [INFO] : jdom:jdom:jar:b9
> [INFO] ant:ant:jar:1.6.5
> [INFO] commons-digester:commons-digester:jar:1.8
> [INFO] javax.mail:mail:jar:1.4
> [INFO] : javax.activation:activation:jar:1.1
> [INFO] xml-apis:xml-apis:jar:1.0.b2
> [INFO] junit:junit:jar:3.8.1
> [INFO] javax.servlet:servlet-api:jar:2.4
> [INFO] xerces:xercesImpl:jar:2.3.0
> [INFO] commons-pool:commons-pool:jar:1.1
> [INFO] commons-beanutils:commons-beanutils:jar:1.7.0
> [INFO] mockobjects:mockobjects-core:jar:0.09
> [INFO] commons-codec:commons-codec:jar:1.3
> [INFO] commons-logging:commons-logging:jar:1.1
> [INFO] hsqldb:hsqldb:jar:1.7.2.2
> [INFO] commons-dbcp:commons-dbcp:jar:1.2.2
> [INFO] xalan:xalan:jar:2.7.0
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Mon Nov 05 22:14:25 CET 2007
> [INFO] Final Memory: 2M/5M
> [INFO] ------------------------------------------------------------------------
>
> The only difference running the tests with Maven now is that exception's
> stack trace is printed to the screen instead of written into a log file
> (because of the now missing log4j dependency).
>
Ok, I will apply this patch to pom.xml. What about the maven 1 build?
Should it be tweaked, too?
Thanks
Oliver
>
>>> Site glitches:
>>> - broken link in "Howtos (1.2 release)" exists a broken link to the
>>> current "User's Guide"
>>> - download page has no entry for version 1.5 (yet ?)
>>> - changes state version 1.5 to be in SVN ... don't forget entry in POM
>> This is a problem of our release process because I cannot anticipate the
>> real release date. So I intend to fill the date in before the final site
>> gets deployed. But of course I must not forget this.
>
> I thought so ;-)
>
>>> - findbugs report ... open issues ??
>> The majority of these issues refers to generated code in the plist
>> package. I will try to find a way how these classes can be excluded.
>
> OK. I was not aware that the criticized code has been generated.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Jörg Schaible <jo...@gmx.de>.
Oliver Heger wrote:
> Hi Jörg,
>
> thanks for the comments.
>
> Jörg Schaible wrote:
>> Hi Oliver,
>>
> <snip/>
>>
>> src package compiles and runs tests on my compiler zoo, fine!
>>
>> Dependencies:
>> - pom uses commons-logging:commons-logging-api instead of
>> commons-logging:commons-logging. The API version should only be used when
>> building a server like Tomcat (IIRC)
>> - because of this we have both commons-logging-api-1.0.4 and
>> commons-logging-1.1 (as transitive dep from digester) in the classpath.
>> Maybe we should directly upgrade to 1.1.1 to drop the optional deps of
>> JCL
> 1.1.1 is not available yet. Would it help to upgrade to 1.1 in the
> meantime?
Oh, well, since we already voted, I thought it had happened :)
Dennis, any time frame?
JCL 1.1 declares compile-time deps to avalon-framework, log4j, logkit and
javax.servlet:servlet-api. We can exlude them (or redeclare them as
optional/provided in case of avalon-framework and servlet-api).
>> - commons-jxpath triggers old xerces-1.2.3, ant-optional and jdom. At
>> least the first two should be possibly excluded, especially since the
>> dependencies page refers xerces-2.2.0 and the pom refers an optional
>> ant-1.6.5
> How can this be achieved? The dependency to jxpath has already been
> marked as optional. What further steps need to be performed?
xerces:xerces should be excluded, since JCC refers newer artifacts of xerces
(with different groupId)
ant-optional possibly also, unfortunately this artifact not even exists in
1.6.x series since it has been splitted.
Current deps:
joehni@paddy ~/java/commons-configuration-1.5-src $ mvn info:deps-test
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'info'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Commons Configuration
[INFO] task-segment: [info:deps-test]
[INFO] ----------------------------------------------------------------------------
[WARNING] POM for 'commons-codec:commons-codec:pom:1.3:compile' is invalid.
It will be ignored for artifact resolution. Reason: Failed to validate POM
[WARNING]
Artifact xml-apis:xml-apis:jar:1.0.b2:provided retains local
scope 'provided' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove the
local scope.
[WARNING]
Artifact junit:junit:jar:3.8.1:test retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove the
local scope.
[INFO] [info:deps-test]
[INFO] commons-configuration:commons-configuration:jar:1.5
[INFO] commons-collections:commons-collections:jar:3.2
[INFO] mockobjects:mockobjects-jdk1.4-j2ee1.3:jar:0.09
[INFO] dbunit:dbunit:jar:2.1
[INFO] commons-lang:commons-lang:jar:2.3
[INFO] junit-addons:junit-addons:jar:1.4
[INFO] : xerces:xmlParserAPIs:jar:2.6.2
[INFO] ant:ant:jar:1.6.5
[INFO] commons-jxpath:commons-jxpath:jar:1.2
[INFO] : xerces:xerces:jar:1.2.3
[INFO] : ant:ant-optional:jar:1.5.1
[INFO] : jdom:jdom:jar:b9
[INFO] commons-digester:commons-digester:jar:1.8
[INFO] : commons-logging:commons-logging:jar:1.1
[INFO] : logkit:logkit:jar:1.0.1
[INFO] : log4j:log4j:jar:1.2.12
[INFO] : avalon-framework:avalon-framework:jar:4.1.3
[INFO] javax.mail:mail:jar:1.4
[INFO] : javax.activation:activation:jar:1.1
[INFO] xml-apis:xml-apis:jar:1.0.b2
[INFO] junit:junit:jar:3.8.1
[INFO] javax.servlet:servlet-api:jar:2.4
[INFO] commons-logging:commons-logging-api:jar:1.0.4
[INFO] xerces:xercesImpl:jar:2.3.0
[INFO] commons-pool:commons-pool:jar:1.1
[INFO] commons-beanutils:commons-beanutils:jar:1.7.0
[INFO] mockobjects:mockobjects-core:jar:0.09
[INFO] commons-codec:commons-codec:jar:1.3
[INFO] hsqldb:hsqldb:jar:1.7.2.2
[INFO] xalan:xalan:jar:2.7.0
[INFO] commons-dbcp:commons-dbcp:jar:1.2.2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
Applying this patch:
==================== %< ================
joehni@paddy ~/java/commons-configuration-1.5-src $ diff -u pom.xml pom.new
--- pom.xml 2007-11-01 15:13:40.000000000 +0100
+++ pom.new 2007-11-05 22:12:41.546284773 +0100
@@ -202,8 +202,23 @@
<dependency>
<groupId>commons-logging</groupId>
- <artifactId>commons-logging-api</artifactId>
- <version>1.0.4</version>
+ <artifactId>commons-logging</artifactId>
+ <version>1.1</version>
+ <!-- remove exclusions for JCL 1.1.1 -->
+ <exclusions>
+ <exclusion>
+ <groupId>logkit</groupId>
+ <artifactId>logkit</artifactId>
+ </exclusion>
+ <exclusion>
+ <groupId>log4j</groupId>
+ <artifactId>log4j</artifactId>
+ </exclusion>
+ <exclusion>
+ <groupId>avalon-framework</groupId>
+ <artifactId>avalon-framework</artifactId>
+ </exclusion>
+ </exclusions>
</dependency>
<dependency>
@@ -230,6 +245,16 @@
<artifactId>commons-jxpath</artifactId>
<version>1.2</version>
<optional>true</optional>
+ <exclusions>
+ <exclusion>
+ <groupId>xerces</groupId>
+ <artifactId>xerces</artifactId>
+ </exclusion>
+ <exclusion>
+ <groupId>ant</groupId>
+ <artifactId>ant-optional</artifactId>
+ </exclusion>
+ </exclusions>
</dependency>
<dependency>
@@ -311,6 +336,12 @@
<artifactId>junit-addons</artifactId>
<version>1.4</version>
<scope>test</scope>
+ <exclusions>
+ <exclusion>
+ <groupId>xerces</groupId>
+ <artifactId>xmlParserAPIs</artifactId>
+ </exclusion>
+ </exclusions>
</dependency>
<dependency>
==================== %< ================
You end up with this deps:
joehni@paddy ~/java/commons-configuration-1.5-src $ mvn -f pom.new
info:deps-test
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'info'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Commons Configuration
[INFO] task-segment: [info:deps-test]
[INFO] ----------------------------------------------------------------------------
[WARNING] POM for 'commons-codec:commons-codec:pom:1.3:compile' is invalid.
It will be ignored for artifact resolution. Reason: Failed to validate POM
[WARNING]
Artifact xml-apis:xml-apis:jar:1.0.b2:provided retains local
scope 'provided' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove the
local scope.
[WARNING]
Artifact junit:junit:jar:3.8.1:test retains local scope 'test'
overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove the
local scope.
[INFO] [info:deps-test]
[INFO] commons-configuration:commons-configuration:jar:1.5
[INFO] commons-collections:commons-collections:jar:3.2
[INFO] mockobjects:mockobjects-jdk1.4-j2ee1.3:jar:0.09
[INFO] dbunit:dbunit:jar:2.1
[INFO] commons-lang:commons-lang:jar:2.3
[INFO] junit-addons:junit-addons:jar:1.4
[INFO] commons-jxpath:commons-jxpath:jar:1.2
[INFO] : jdom:jdom:jar:b9
[INFO] ant:ant:jar:1.6.5
[INFO] commons-digester:commons-digester:jar:1.8
[INFO] javax.mail:mail:jar:1.4
[INFO] : javax.activation:activation:jar:1.1
[INFO] xml-apis:xml-apis:jar:1.0.b2
[INFO] junit:junit:jar:3.8.1
[INFO] javax.servlet:servlet-api:jar:2.4
[INFO] xerces:xercesImpl:jar:2.3.0
[INFO] commons-pool:commons-pool:jar:1.1
[INFO] commons-beanutils:commons-beanutils:jar:1.7.0
[INFO] mockobjects:mockobjects-core:jar:0.09
[INFO] commons-codec:commons-codec:jar:1.3
[INFO] commons-logging:commons-logging:jar:1.1
[INFO] hsqldb:hsqldb:jar:1.7.2.2
[INFO] commons-dbcp:commons-dbcp:jar:1.2.2
[INFO] xalan:xalan:jar:2.7.0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Nov 05 22:14:25 CET 2007
[INFO] Final Memory: 2M/5M
[INFO] ------------------------------------------------------------------------
The only difference running the tests with Maven now is that exception's
stack trace is printed to the screen instead of written into a log file
(because of the now missing log4j dependency).
>> Site glitches:
>> - broken link in "Howtos (1.2 release)" exists a broken link to the
>> current "User's Guide"
>> - download page has no entry for version 1.5 (yet ?)
>> - changes state version 1.5 to be in SVN ... don't forget entry in POM
> This is a problem of our release process because I cannot anticipate the
> real release date. So I intend to fill the date in before the final site
> gets deployed. But of course I must not forget this.
I thought so ;-)
>> - findbugs report ... open issues ??
> The majority of these issues refers to generated code in the plist
> package. I will try to find a way how these classes can be excluded.
OK. I was not aware that the criticized code has been generated.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by nicolas de loof <ni...@gmail.com>.
About dependencies in the POM :
servletapi has been relocated to javax.servlet : servlet-api
This one should also be set as <scope>provided</scope>, as it is provided by
the servlet engine.
Not sure if this is the same case for javax.mail:mail. In an
application-server context this one is provided, but not in a standalone
(batch) context. For the latter case, any batch project would have to
declare dependencies on server-side java API it uses anyway.
Is there a good reason to use commons-beanutils-core and not the (more
popular) commons-beanutils ?
For many projects, this will introduce duplicate commons-beanutils* jars as
many other libraries declare dependency on commons-beanutils.
Nico.
2007/11/4, Oliver Heger <ol...@oliver-heger.de>:
>
> Hi Jörg,
>
> thanks for the comments.
>
> Jörg Schaible wrote:
> > Hi Oliver,
> >
> <snip/>
> >
> > src package compiles and runs tests on my compiler zoo, fine!
> >
> > Dependencies:
> > - pom uses commons-logging:commons-logging-api instead of
> > commons-logging:commons-logging. The API version should only be used
> when
> > building a server like Tomcat (IIRC)
> > - because of this we have both commons-logging-api-1.0.4 and
> > commons-logging-1.1 (as transitive dep from digester) in the classpath.
> > Maybe we should directly upgrade to 1.1.1 to drop the optional deps of
> JCL
> 1.1.1 is not available yet. Would it help to upgrade to 1.1 in the
> meantime?
>
> > - commons-jxpath triggers old xerces-1.2.3, ant-optional and jdom. At
> least
> > the first two should be possibly excluded, especially since the
> > dependencies page refers xerces-2.2.0 and the pom refers an optional
> > ant-1.6.5
> How can this be achieved? The dependency to jxpath has already been
> marked as optional. What further steps need to be performed?
>
> >
> >
> > Site glitches:
> > - broken link in "Howtos (1.2 release)" exists a broken link to the
> > current "User's Guide"
> > - download page has no entry for version 1.5 (yet ?)
> > - changes state version 1.5 to be in SVN ... don't forget entry in POM
> This is a problem of our release process because I cannot anticipate the
> real release date. So I intend to fill the date in before the final site
> gets deployed. But of course I must not forget this.
>
> > - findbugs report ... open issues ??
> The majority of these issues refers to generated code in the plist
> package. I will try to find a way how these classes can be excluded.
>
> Oliver
>
> >
> >
> > Cheers,
> > Jörg
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Hi Jörg,
thanks for the comments.
Jörg Schaible wrote:
> Hi Oliver,
>
<snip/>
>
> src package compiles and runs tests on my compiler zoo, fine!
>
> Dependencies:
> - pom uses commons-logging:commons-logging-api instead of
> commons-logging:commons-logging. The API version should only be used when
> building a server like Tomcat (IIRC)
> - because of this we have both commons-logging-api-1.0.4 and
> commons-logging-1.1 (as transitive dep from digester) in the classpath.
> Maybe we should directly upgrade to 1.1.1 to drop the optional deps of JCL
1.1.1 is not available yet. Would it help to upgrade to 1.1 in the meantime?
> - commons-jxpath triggers old xerces-1.2.3, ant-optional and jdom. At least
> the first two should be possibly excluded, especially since the
> dependencies page refers xerces-2.2.0 and the pom refers an optional
> ant-1.6.5
How can this be achieved? The dependency to jxpath has already been
marked as optional. What further steps need to be performed?
>
>
> Site glitches:
> - broken link in "Howtos (1.2 release)" exists a broken link to the
> current "User's Guide"
> - download page has no entry for version 1.5 (yet ?)
> - changes state version 1.5 to be in SVN ... don't forget entry in POM
This is a problem of our release process because I cannot anticipate the
real release date. So I intend to fill the date in before the final site
gets deployed. But of course I must not forget this.
> - findbugs report ... open issues ??
The majority of these issues refers to generated code in the plist
package. I will try to find a way how these classes can be excluded.
Oliver
>
>
> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Oliver,
Oliver Heger wrote:
> The 1.5 release of Commons Configuration is overdue.
>
> I have prepared a first release candidate. All artifacts including a
> clirr report and the release notes can be found at
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>
> The site is also available under
>
http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>
> Please take the time to have a look at the artifacts and cast your vote.
> I will count the votes not before next Thursday (Nov. 8th).
src package compiles and runs tests on my compiler zoo, fine!
Dependencies:
- pom uses commons-logging:commons-logging-api instead of
commons-logging:commons-logging. The API version should only be used when
building a server like Tomcat (IIRC)
- because of this we have both commons-logging-api-1.0.4 and
commons-logging-1.1 (as transitive dep from digester) in the classpath.
Maybe we should directly upgrade to 1.1.1 to drop the optional deps of JCL
- commons-jxpath triggers old xerces-1.2.3, ant-optional and jdom. At least
the first two should be possibly excluded, especially since the
dependencies page refers xerces-2.2.0 and the pom refers an optional
ant-1.6.5
Site glitches:
- broken link in "Howtos (1.2 release)" exists a broken link to the
current "User's Guide"
- download page has no entry for version 1.5 (yet ?)
- changes state version 1.5 to be in SVN ... don't forget entry in POM
- findbugs report ... open issues ??
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Rahul Akolkar wrote:
> Is this vote open?
>
> -Rahul
>
There have been some remarks and suggestions for improvements related to
the maven build files and the site. So I intend to create another RC
soon (probably at the weekend).
This vote is closed.
Thanks
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Rahul Akolkar <ra...@gmail.com>.
Is this vote open?
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Michiel Kalkman wrote:
> Also, do you want to keep the old link to Avalon ? (just nipicking)
This link obviously does not have much value. I think I will remove it
after the release (or if another release candidate should be required).
Oliver
>
> On 11/1/07, Oliver Heger <ol...@oliver-heger.de> wrote:
>
>>The 1.5 release of Commons Configuration is overdue.
>>
>>I have prepared a first release candidate. All artifacts including a
>>clirr report and the release notes can be found at
>>http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>>
>>The site is also available under
>>http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>>
>>Please take the time to have a look at the artifacts and cast your vote.
>>I will count the votes not before next Thursday (Nov. 8th).
>>
>>Thanks.
>>Oliver
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Michiel Kalkman <mi...@gmail.com>.
Also, do you want to keep the old link to Avalon ? (just nipicking)
On 11/1/07, Oliver Heger <ol...@oliver-heger.de> wrote:
> The 1.5 release of Commons Configuration is overdue.
>
> I have prepared a first release candidate. All artifacts including a
> clirr report and the release notes can be found at
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>
> The site is also available under
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>
> Please take the time to have a look at the artifacts and cast your vote.
> I will count the votes not before next Thursday (Nov. 8th).
>
> Thanks.
> Oliver
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Niall Pemberton <ni...@gmail.com>.
On Nov 8, 2007 9:01 PM, Oliver Heger <ol...@oliver-heger.de> wrote:
>
> Niall Pemberton wrote:
> > On Nov 1, 2007 3:04 PM, Oliver Heger <ol...@oliver-heger.de> wrote:
> >> The 1.5 release of Commons Configuration is overdue.
> >>
> >> I have prepared a first release candidate. All artifacts including a
> >> clirr report and the release notes can be found at
> >> http://people.apache.org/~oheger/commons-configuration-1.5rc1/
> >>
> >> The site is also available under
> >> http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
> >>
> >> Please take the time to have a look at the artifacts and cast your vote.
> >> I will count the votes not before next Thursday (Nov. 8th).
> >
> > The only thing that looked slightly strange to me was that the distros
> > appear to be built with m1 but the jar manifest indicates it was built
> > with ant. When I tried building with m1 and JDK 1.3 though I hit the
> > issue of java.sql.Datasource not being present in JDK 1.3 - so I guess
> > thats the reason. I added JDK 1.3 source/target to the m1 build so
> > that later JDKs create compatible builds.
> >
> > Anyway looks good to me so +1.
> >
> > Niall
> >
> > P.S. I also added site and assembly descriptors for the m2 build,
> > which IMO don't matter for this release, but good for the future.
> >
> >> Thanks.
> >> Oliver
> >
>
> Niall,
>
> thanks for your support, especially the improvements of the m2 build.
>
> I usually build with maven 1 on a JDK 1.3. The site contains some
> information about how to build with this constellation (the "building"
> link). No idea why the manifest has an entry about ant.
>
> With the source/target declarations in project.properties I have a
> problem: javac from JDK 1.3 does not understand the source option and
> causes an error. This is the reason why these flags were not set before.
> Do you know a workaround for this issue?
I'm not aware of the issue. I just tried building with JDK 1.3.1_18
(from Sun) and maven1 with the source/target options set to 1.3. Once
I followed the instructions for "dependency.jdbc" and ran with the
"-Dmaven.test.skip=true" the only problems I had were with the
checkstyle and findbugs plugins which were created with later JDK
versions - commenting those out and it built fine.
Seems though that the maven1 build for Commons Configuration has so
many JDK 1.3 gotchas that having the source/target options set and
building with JDK 1.4+ would be the best option for anyone else
wanting to build from source.
Niall
> Because of the changes that have been made at the build files I plan to
> create another RC soon.
>
>
> Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Oliver Heger <ol...@oliver-heger.de>.
Niall Pemberton wrote:
> On Nov 1, 2007 3:04 PM, Oliver Heger <ol...@oliver-heger.de> wrote:
>> The 1.5 release of Commons Configuration is overdue.
>>
>> I have prepared a first release candidate. All artifacts including a
>> clirr report and the release notes can be found at
>> http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>>
>> The site is also available under
>> http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>>
>> Please take the time to have a look at the artifacts and cast your vote.
>> I will count the votes not before next Thursday (Nov. 8th).
>
> The only thing that looked slightly strange to me was that the distros
> appear to be built with m1 but the jar manifest indicates it was built
> with ant. When I tried building with m1 and JDK 1.3 though I hit the
> issue of java.sql.Datasource not being present in JDK 1.3 - so I guess
> thats the reason. I added JDK 1.3 source/target to the m1 build so
> that later JDKs create compatible builds.
>
> Anyway looks good to me so +1.
>
> Niall
>
> P.S. I also added site and assembly descriptors for the m2 build,
> which IMO don't matter for this release, but good for the future.
>
>> Thanks.
>> Oliver
>
Niall,
thanks for your support, especially the improvements of the m2 build.
I usually build with maven 1 on a JDK 1.3. The site contains some
information about how to build with this constellation (the "building"
link). No idea why the manifest has an entry about ant.
With the source/target declarations in project.properties I have a
problem: javac from JDK 1.3 does not understand the source option and
causes an error. This is the reason why these flags were not set before.
Do you know a workaround for this issue?
Because of the changes that have been made at the build files I plan to
create another RC soon.
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Commons Configuration 1.5 based on RC1
Posted by Niall Pemberton <ni...@gmail.com>.
On Nov 1, 2007 3:04 PM, Oliver Heger <ol...@oliver-heger.de> wrote:
> The 1.5 release of Commons Configuration is overdue.
>
> I have prepared a first release candidate. All artifacts including a
> clirr report and the release notes can be found at
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/
>
> The site is also available under
> http://people.apache.org/~oheger/commons-configuration-1.5rc1/site/index.html
>
> Please take the time to have a look at the artifacts and cast your vote.
> I will count the votes not before next Thursday (Nov. 8th).
The only thing that looked slightly strange to me was that the distros
appear to be built with m1 but the jar manifest indicates it was built
with ant. When I tried building with m1 and JDK 1.3 though I hit the
issue of java.sql.Datasource not being present in JDK 1.3 - so I guess
thats the reason. I added JDK 1.3 source/target to the m1 build so
that later JDKs create compatible builds.
Anyway looks good to me so +1.
Niall
P.S. I also added site and assembly descriptors for the m2 build,
which IMO don't matter for this release, but good for the future.
> Thanks.
> Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org