svn commit: r493682 - /jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/ClassUtilsTest.java

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 00:15:41 2007
New Revision: 493682

URL: http://svn.apache.org/viewvc?view=revrev=493682
Log:
Change the assertion failure messages to provide more info

Modified:

jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/ClassUtilsTest.java

Modified: 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/ClassUtilsTest.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/ClassUtilsTest.java?view=diffrev=493682r1=493681r2=493682
==
--- 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/ClassUtilsTest.java
 (original)
+++ 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/ClassUtilsTest.java
 Sun Jan  7 00:15:41 2007
@@ -513,13 +513,13 @@
 ClassLoader systemClassLoader = ClassLoader.getSystemClassLoader();
 ClassLoader myClassLoader = ClassUtilsTest.class.getClassLoader();
 if (!(myClassLoader instanceof URLClassLoader)) {
-fail(Need a better test set up.);
+fail(ClassUtilsTest ClassLoader =  + (myClassLoader == null ? 
null : myClassLoader.getClass().getName()));
 }
 if (!(systemClassLoader instanceof URLClassLoader)) {
-fail(Need a better test set up.);
+fail(System  ClassLoader =  + (systemClassLoader == null ? null 
: systemClassLoader.getClass().getName()));
 }
 if (!myClassLoader.equals(systemClassLoader)) {
-fail(Need a better test set up?);
+fail(ClassUtilsTest=  + myClassLoader +  System= + 
systemClassLoader);
 }
 URLClassLoader urlScl = (URLClassLoader) myClassLoader;
 return URLClassLoader.newInstance(urlScl.getURLs(), null);



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-transaction (in module jakarta-commons) failed

2007-01-07 Thread Adam Jack
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-transaction has an issue affecting its community integration.
This issue affects 20 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-ojb :  Commons Jelly
- commons-transaction :  Commons Identifier Package
- commons-vfs :  Jakarta commons
- db-ojb :  ObjectRelationalBridge
- db-ojb-from-packages :  ObjectRelationalBridge
- excalibur-fortress-bean :  Repository of reusable components.
- excalibur-fortress-container-impl :  Repository of reusable components.
- excalibur-fortress-container-test :  Repository of reusable components.
- excalibur-fortress-examples :  Repository of reusable components.
- excalibur-fortress-migration :  Repository of reusable components.
- excalibur-fortress-platform :  Repository of reusable components.
- excalibur-fortress-testcase :  Repository of reusable components.
- excalibur-monitor :  Repository of reusable components.
- excalibur-sourceresolve :  Repository of reusable components.
- excalibur-xmlutil :  Repository of reusable components.
- ivy :  Ivy Core
- jakarta-slide :  Content Management System based on WebDAV technology
- logging-log4j-chainsaw :  Chainsaw log viewer
- slide-webdavclient :  Content Management System based on WebDAV technology
- test-ojb :  ObjectRelationalBridge


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-transaction/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-transaction-07012007.jar] identifier set to 
project name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons/commons-transaction/gump_work/build_jakarta-commons_commons-transaction.html
Work Name: build_jakarta-commons_commons-transaction (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion=07012007 jar 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-commons/transaction]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-07012007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/packages/j2ee_connector-1_5-fr/connector-api.jar:/usr/local/gump/packages/jta-spec1_0_1/jta-spec1_0_1.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
Buildfile: build.xml

detect.display:
 [echo] +---
 [echo] | Build environment for commons-transaction 07012007
 [echo] | 
 [echo] | Note: 
 [echo] |   If ${property.name} is displayed for a library 
 [echo] |   instead of 'true', that library is not present.
 [echo] +---
 [echo] 
 [echo] Environment:
 [echo]   Java home
/x1/opt/__versions__/jdk1.5.0_06/jre
 [echo]   Java version 1.5
 [echo] 
 [echo] Build options:
 [echo]   Generate debugging info  true
 [echo]   Display deprecation info true
 [echo]   Optimize true
 [echo] 
 [echo] Directories:
 [echo]   Build directory  
/x1/gump/public/workspace/jakarta-commons/transaction/build
 [echo]   Distribution directory   
/x1/gump/public/workspace/jakarta-commons/transaction/dist
 [echo]   JBoss deploy directory   ${jboss.deploy.dir}
 [echo] 
 [echo] Optional Libraries:
 [echo]   

[EMAIL PROTECTED]: Project commons-transaction (in module jakarta-commons) failed

2007-01-07 Thread Adam Jack
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-transaction has an issue affecting its community integration.
This issue affects 20 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-ojb :  Commons Jelly
- commons-transaction :  Commons Identifier Package
- commons-vfs :  Jakarta commons
- db-ojb :  ObjectRelationalBridge
- db-ojb-from-packages :  ObjectRelationalBridge
- excalibur-fortress-bean :  Repository of reusable components.
- excalibur-fortress-container-impl :  Repository of reusable components.
- excalibur-fortress-container-test :  Repository of reusable components.
- excalibur-fortress-examples :  Repository of reusable components.
- excalibur-fortress-migration :  Repository of reusable components.
- excalibur-fortress-platform :  Repository of reusable components.
- excalibur-fortress-testcase :  Repository of reusable components.
- excalibur-monitor :  Repository of reusable components.
- excalibur-sourceresolve :  Repository of reusable components.
- excalibur-xmlutil :  Repository of reusable components.
- ivy :  Ivy Core
- jakarta-slide :  Content Management System based on WebDAV technology
- logging-log4j-chainsaw :  Chainsaw log viewer
- slide-webdavclient :  Content Management System based on WebDAV technology
- test-ojb :  ObjectRelationalBridge


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-transaction/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-transaction-07012007.jar] identifier set to 
project name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons/commons-transaction/gump_work/build_jakarta-commons_commons-transaction.html
Work Name: build_jakarta-commons_commons-transaction (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion=07012007 jar 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-commons/transaction]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/codec/dist/commons-codec-07012007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/packages/j2ee_connector-1_5-fr/connector-api.jar:/usr/local/gump/packages/jta-spec1_0_1/jta-spec1_0_1.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
Buildfile: build.xml

detect.display:
 [echo] +---
 [echo] | Build environment for commons-transaction 07012007
 [echo] | 
 [echo] | Note: 
 [echo] |   If ${property.name} is displayed for a library 
 [echo] |   instead of 'true', that library is not present.
 [echo] +---
 [echo] 
 [echo] Environment:
 [echo]   Java home
/x1/opt/__versions__/jdk1.5.0_06/jre
 [echo]   Java version 1.5
 [echo] 
 [echo] Build options:
 [echo]   Generate debugging info  true
 [echo]   Display deprecation info true
 [echo]   Optimize true
 [echo] 
 [echo] Directories:
 [echo]   Build directory  
/x1/gump/public/workspace/jakarta-commons/transaction/build
 [echo]   Distribution directory   
/x1/gump/public/workspace/jakarta-commons/transaction/dist
 [echo]   JBoss deploy directory   ${jboss.deploy.dir}
 [echo] 
 [echo] Optional Libraries:
 [echo]   

[nightly build] betwixt finder failed.

2007-01-07 Thread psteitz
Failed build logs:
http://people.apache.org/~psteitz/commons-nightlies/20070107/betwixt.log
http://people.apache.org/~psteitz/commons-nightlies/20070107/finder.log

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [nightly build] betwixt finder failed.

2007-01-07 Thread Dennis Lundberg

[EMAIL PROTECTED] wrote:

Failed build logs:
http://people.apache.org/~psteitz/commons-nightlies/20070107/betwixt.log
http://people.apache.org/~psteitz/commons-nightlies/20070107/finder.log


The Maven 2 installation running the nightly builds needs to upgrade its 
jar-plugin to version 2.1, otherwise Phil's changes to the parent pom 
will cause this failure for finder or other M2 builds.


--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493704 - /jakarta/commons/proper/betwixt/trunk/src/test/org/apache/commons/betwixt/TestRSSRoundTrip.java

2007-01-07 Thread rdonkin
Author: rdonkin
Date: Sun Jan  7 04:17:19 2007
New Revision: 493704

URL: http://svn.apache.org/viewvc?view=revrev=493704
Log:
Netscape has removed the DTD. Removed test that depends on RSS 0.91.

Removed:

jakarta/commons/proper/betwixt/trunk/src/test/org/apache/commons/betwixt/TestRSSRoundTrip.java


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [nightly build] betwixt failed.

2007-01-07 Thread robert burrell donkin
On Sun, 2007-01-07 at 03:19 +0100, Dennis Lundberg wrote:
 [EMAIL PROTECTED] wrote:
  Failed build logs:
  http://people.apache.org/~psteitz/commons-nightlies/20070106/betwixt.log
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 It seems that Netscape [1] has decided to take down the site where the 
 rss-0.91.dtd file [2] is located. I googled for an alternate location 
 and found one on freshmeat [3].
 
 [1] http://my.netscape.com/
 [2] http://my.netscape.com/publish/formats/rss-0.91.dtd
 [3] http://download.freshmeat.net/backend/rss-0.91.dtd

the licensing for 0.91 is interesting (to say the least) which is why we can't 
distribute it

removing the test seemed like the best idea so that's what i've done 

- robert



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-betwixt (in module jakarta-commons) failed

2007-01-07 Thread James Strachan
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-betwixt has an issue affecting its community integration.
This issue affects 4 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-betwixt :  Commons Betwixt Package
- commons-jelly-tags-betwixt :  Commons Jelly
- db-ddlutils :  Easy-to-use component for working with Database Definition 
(...
- maven-bootstrap :  Project Management Tools


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-betwixt/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-betwixt-07012007.jar] identifier set to project 
name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons/commons-betwixt/gump_work/build_jakarta-commons_commons-betwixt.html
Work Name: build_jakarta-commons_commons-betwixt (Type: Build)
Work ended in a state of : Failed
Elapsed: 57 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dfinal.name=commons-betwixt-07012007 
-Dresourcedir=/usr/local/gump/public/workspace/jakarta-commons/betwixt jar 
[Working Directory: /usr/local/gump/public/workspace/jakarta-commons/betwixt]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/betwixt/target/classes:/usr/local/gump/public/workspace/jakarta-commons/betwixt/target/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-07012007.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Running org.apache.commons.betwixt.TestOptions
[junit] Testsuite: org.apache.commons.betwixt.TestOptions
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.254 sec
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.254 sec
[junit] 
[junit] Testcase: testGetValue took 0.007 sec
[junit] Testcase: testGetNames took 0.002 sec
[junit] Testcase: testAddOptions took 0.002 sec
[junit] Running org.apache.commons.betwixt.TestRSSRoundTrip
[junit] Testsuite: org.apache.commons.betwixt.TestRSSRoundTrip
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 21.251 sec
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 21.251 sec
[junit] 
[junit] Testcase: testRoundTrip took 20.977 sec
[junit] Caused an ERROR
[junit] my.netscape.com
[junit] java.net.UnknownHostException: my.netscape.com
[junit] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
[junit] at java.net.Socket.connect(Socket.java:507)
[junit] at java.net.Socket.connect(Socket.java:457)
[junit] at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
[junit] at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
[junit] at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
[junit] at sun.net.www.http.HttpClient.init(HttpClient.java:214)
[junit] at sun.net.www.http.HttpClient.New(HttpClient.java:287)
[junit] at sun.net.www.http.HttpClient.New(HttpClient.java:299)
[junit] at 

[EMAIL PROTECTED]: Project commons-betwixt (in module jakarta-commons) failed

2007-01-07 Thread James Strachan
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-betwixt has an issue affecting its community integration.
This issue affects 4 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-betwixt :  Commons Betwixt Package
- commons-jelly-tags-betwixt :  Commons Jelly
- db-ddlutils :  Easy-to-use component for working with Database Definition 
(...
- maven-bootstrap :  Project Management Tools


Full details are available at:

http://vmgump.apache.org/gump/public/jakarta-commons/commons-betwixt/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-betwixt-07012007.jar] identifier set to project 
name
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-commons/commons-betwixt/gump_work/build_jakarta-commons_commons-betwixt.html
Work Name: build_jakarta-commons_commons-betwixt (Type: Build)
Work ended in a state of : Failed
Elapsed: 57 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dfinal.name=commons-betwixt-07012007 
-Dresourcedir=/usr/local/gump/public/workspace/jakarta-commons/betwixt jar 
[Working Directory: /usr/local/gump/public/workspace/jakarta-commons/betwixt]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/betwixt/target/classes:/usr/local/gump/public/workspace/jakarta-commons/betwixt/target/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-07012007.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Running org.apache.commons.betwixt.TestOptions
[junit] Testsuite: org.apache.commons.betwixt.TestOptions
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.254 sec
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.254 sec
[junit] 
[junit] Testcase: testGetValue took 0.007 sec
[junit] Testcase: testGetNames took 0.002 sec
[junit] Testcase: testAddOptions took 0.002 sec
[junit] Running org.apache.commons.betwixt.TestRSSRoundTrip
[junit] Testsuite: org.apache.commons.betwixt.TestRSSRoundTrip
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 21.251 sec
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 21.251 sec
[junit] 
[junit] Testcase: testRoundTrip took 20.977 sec
[junit] Caused an ERROR
[junit] my.netscape.com
[junit] java.net.UnknownHostException: my.netscape.com
[junit] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
[junit] at java.net.Socket.connect(Socket.java:507)
[junit] at java.net.Socket.connect(Socket.java:457)
[junit] at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
[junit] at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
[junit] at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
[junit] at sun.net.www.http.HttpClient.init(HttpClient.java:214)
[junit] at sun.net.www.http.HttpClient.New(HttpClient.java:287)
[junit] at sun.net.www.http.HttpClient.New(HttpClient.java:299)
[junit] at 

Re: [all] jarfiles in svn

2007-01-07 Thread Joerg Heinicke
Simon Kitching skitching at apache.org writes:

 For a start, if every project were to do this, the impact on the
 Apache SVN repository would be huge.

Cocoon (maintenance branch 2.1) has currently 111 jars with about 40 MB in its
repository (+ the one for the environment [2]), we are regularly upgrading them
and it has never been seen as a problem from infrastructure team.

 I would instead prefer to see ant builds using get to download jars as
 needed. The maven repositories can be used as a convenient source for
 the jars, eg
 http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/build.xml

I posted my opinion on this recently [3]:
In general I don't like the need for internet access on build time. But with Ant
it's at least better than with Maven as the build environment itself does not
get changed.

My concerns are raised after one year mess with Maven in Cocoon trunk.

Regards
Jörg

[1] http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/lib/
[2] http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/tools/lib/
[3] http://marc.theaimsgroup.com/?l=jakarta-commons-devm=116811395603150w=4


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493706 - /jakarta/commons/sandbox/i18n/trunk/pom.xml

2007-01-07 Thread dennisl
Author: dennisl
Date: Sun Jan  7 04:31:46 2007
New Revision: 493706

URL: http://svn.apache.org/viewvc?view=revrev=493706
Log:
Turn off FindBugs report due to LGPL dependency issue.

Modified:
jakarta/commons/sandbox/i18n/trunk/pom.xml

Modified: jakarta/commons/sandbox/i18n/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/sandbox/i18n/trunk/pom.xml?view=diffrev=493706r1=493705r2=493706
==
--- jakarta/commons/sandbox/i18n/trunk/pom.xml (original)
+++ jakarta/commons/sandbox/i18n/trunk/pom.xml Sun Jan  7 04:31:46 2007
@@ -122,10 +122,12 @@
   /reportSet
 /reportSets
   /plugin
+  !--
   plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdfindbugs-maven-plugin/artifactId
   /plugin
+  --
 /plugins
   /reporting
   distributionManagement



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [EMAIL PROTECTED]: Project commons-transaction (in module jakarta-commons) failed

2007-01-07 Thread Joerg Heinicke
Adam Jack ajack at apache.org writes:

 Project commons-transaction has an issue affecting its community integration.
 This issue affects 20 projects.
 The current state of this project is 'Failed', with reason 'Build Failed'.

Will have a look on this.

Jörg


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493707 - in /jakarta/commons/proper/commons-build/trunk/samples: ./ pom.xml.sample sandbox-pom.xml.sample

2007-01-07 Thread dennisl
Author: dennisl
Date: Sun Jan  7 04:37:57 2007
New Revision: 493707

URL: http://svn.apache.org/viewvc?view=revrev=493707
Log:
Add sample pom.xml files for proper and sandbox components.

Added:
jakarta/commons/proper/commons-build/trunk/samples/
jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample   (with 
props)
jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample   
(with props)

Added: jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample?view=autorev=493707
==
--- jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample (added)
+++ jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample Sun Jan  
7 04:37:57 2007
@@ -0,0 +1,65 @@
+?xml version=1.0 encoding=UTF-8?
+
+!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+License); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+--
+
+project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
+ xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;
+  parent
+groupIdorg.apache.commons/groupId
+artifactIdcommons-parent/artifactId
+version2-SNAPSHOT/version
+  /parent
+  modelVersion4.0.0/modelVersion
+  artifactIdcommons-foo/artifactId
+  nameCommons Foo/name
+  version1.0-SNAPSHOT/version
+  descriptionDescribe how wonderful this proper component is./description
+  urlhttp://jakarta.apache.org/commons/foo//url
+  issueManagement
+systemjira/system
+urlhttp://issues.apache.org/jira/browse/FOO/url
+  /issueManagement
+  inceptionYear2007/inceptionYear
+  developers/
+  contributors/
+  scm
+
connectionscm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/foo/trunk//connection
+
developerConnectionscm:svn:https://svn.apache.org/repos/asf/jakarta/commons/proper/foo/trunk//developerConnection
+
urlhttp://svn.apache.org/repos/asf/jakarta/commons/proper/foo/trunk//url
+  /scm
+  build/
+  profiles/
+  modules/
+  dependencies/
+  reporting/
+  dependencyManagement/
+  distributionManagement
+site
+  idapache.website/id
+  nameApache Website/name
+  urlscp://people.apache.org/www/jakarta.apache.org/commons/foo//url
+/site
+  /distributionManagement
+  !-- Compiler source and target JVM (see parent pom) --
+  properties
+maven.compile.source1.3/maven.compile.source
+maven.compile.target1.3/maven.compile.target
+  /properties
+/project

Propchange: jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample
--
svn:eol-style = native

Added: jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample?view=autorev=493707
==
--- jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample 
(added)
+++ jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample 
Sun Jan  7 04:37:57 2007
@@ -0,0 +1,61 @@
+?xml version=1.0 encoding=UTF-8?
+
+!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+License); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+--
+
+project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
+ xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 

svn commit: r493709 - in /jakarta/commons/proper/commons-build/trunk: ./ samples/

2007-01-07 Thread dennisl
Author: dennisl
Date: Sun Jan  7 04:39:51 2007
New Revision: 493709

URL: http://svn.apache.org/viewvc?view=revrev=493709
Log:
Move all sample files to the samples directory.

Added:
jakarta/commons/proper/commons-build/trunk/samples/maven.xml.sample
  - copied unchanged from r493697, 
jakarta/commons/proper/commons-build/trunk/maven.xml.sample
jakarta/commons/proper/commons-build/trunk/samples/navigation.xml.sample
  - copied unchanged from r493697, 
jakarta/commons/proper/commons-build/trunk/navigation.xml.sample
jakarta/commons/proper/commons-build/trunk/samples/project.properties.sample
  - copied unchanged from r493697, 
jakarta/commons/proper/commons-build/trunk/project.properties.sample
jakarta/commons/proper/commons-build/trunk/samples/project.xml.sample
  - copied unchanged from r493697, 
jakarta/commons/proper/commons-build/trunk/project.xml.sample
Removed:
jakarta/commons/proper/commons-build/trunk/maven.xml.sample
jakarta/commons/proper/commons-build/trunk/navigation.xml.sample
jakarta/commons/proper/commons-build/trunk/project.properties.sample
jakarta/commons/proper/commons-build/trunk/project.xml.sample


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-soap (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-soap development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-soap has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 34 runs.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-soap :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-soap-07012007.jar] identifier set to 
project name
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on 
Project:commons-jelly-tags-soap
 -DEBUG- Dependency on ws-axis exists, no need to add for property 
maven.jar.axis.
 -DEBUG- Dependency on ws-axis exists, no need to add for property 
maven.jar.jaxrpc-api.
 -DEBUG- Dependency on ws-axis exists, no need to add for property 
maven.jar.saaj-api.
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 1807012007, vmgump.apache.org:vmgump-public:1807012007
Gump E-mail Identifier (unique within run) #31.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-soap (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-soap development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-soap has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 34 runs.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-soap :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-soap-07012007.jar] identifier set to 
project name
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on 
Project:commons-jelly-tags-soap
 -DEBUG- Dependency on ws-axis exists, no need to add for property 
maven.jar.axis.
 -DEBUG- Dependency on ws-axis exists, no need to add for property 
maven.jar.jaxrpc-api.
 -DEBUG- Dependency on ws-axis exists, no need to add for property 
maven.jar.saaj-api.
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 1807012007, vmgump.apache.org:vmgump-public:1807012007
Gump E-mail Identifier (unique within run) #31.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493718 - in /jakarta/commons/proper/commons-build/trunk/samples: sandbox-site.xml.sample site.xml.sample

2007-01-07 Thread dennisl
Author: dennisl
Date: Sun Jan  7 05:26:24 2007
New Revision: 493718

URL: http://svn.apache.org/viewvc?view=revrev=493718
Log:
Add sample site.xml files for proper and sandbox components.

Added:
jakarta/commons/proper/commons-build/trunk/samples/sandbox-site.xml.sample  
 (with props)
jakarta/commons/proper/commons-build/trunk/samples/site.xml.sample   (with 
props)

Added: 
jakarta/commons/proper/commons-build/trunk/samples/sandbox-site.xml.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-build/trunk/samples/sandbox-site.xml.sample?view=autorev=493718
==
--- jakarta/commons/proper/commons-build/trunk/samples/sandbox-site.xml.sample 
(added)
+++ jakarta/commons/proper/commons-build/trunk/samples/sandbox-site.xml.sample 
Sun Jan  7 05:26:24 2007
@@ -0,0 +1,53 @@
+?xml version=1.0 encoding=ISO-8859-1?
+
+!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+License); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+--
+
+project name=Commons Foo
+  bannerRight
+nameCommons Foo/name
+srcimages/logo.png/src
+hrefhttp://jakarta.apache.org/commons/sandbox/foo//href
+  /bannerRight
+  body
+!-- If you want any extra links, add them here, otherwise remove this
+links/
+--
+menu name=Commons Foo
+  !-- Pick the ones that fit your component or add new ones --
+  item name=Overview href=index.html/
+  item name=Downloads href=downloads.html/
+  item name=Examples href=examples.html/
+  item name=FAQ href=faq.html/
+  item name=Javadoc href=apidocs/index.html/
+  item name=User Guide href=userguide.html/
+  item name=Wiki href=http://wiki.apache.org/jakarta-commons/Foo/
+/menu
+!-- Feel free to drop this menu if you don't have these docs --
+menu name=Development
+  !-- Pick the ones that fit your component or add new ones --
+  item name=Building href=building.html/
+  item name=Developer Guide href=developerguide.html/
+/menu
+!-- If you need more menus add them here --
+!-- Use this only if the component has modules, otherwise remove it
+menu ref=modules/
+--
+  /body
+/project

Propchange: 
jakarta/commons/proper/commons-build/trunk/samples/sandbox-site.xml.sample
--
svn:eol-style = native

Added: jakarta/commons/proper/commons-build/trunk/samples/site.xml.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-build/trunk/samples/site.xml.sample?view=autorev=493718
==
--- jakarta/commons/proper/commons-build/trunk/samples/site.xml.sample (added)
+++ jakarta/commons/proper/commons-build/trunk/samples/site.xml.sample Sun Jan  
7 05:26:24 2007
@@ -0,0 +1,54 @@
+?xml version=1.0 encoding=ISO-8859-1?
+
+!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+License); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+--
+
+project name=Commons Foo
+  bannerRight
+nameCommons Foo/name
+srcimages/logo.png/src
+hrefhttp://jakarta.apache.org/commons/foo//href
+  /bannerRight
+  body
+!-- If you want any extra links, add them here, otherwise remove this
+links/
+--
+menu name=Commons Foo
+  !-- Pick the ones that fit your component or add new ones --
+  item name=Overview href=index.html/
+  item name=Downloads 
href=http://jakarta.apache.org/site/downloads/downloads_commons-foo.cgi/
+  item name=Examples href=examples.html/
+  item name=FAQ href=faq.html/
+  item name=Javadoc href=apidocs/index.html/
+ 

svn commit: r493719 - in /jakarta/commons/proper/commons-build/trunk/samples: pom.xml.sample sandbox-pom.xml.sample

2007-01-07 Thread dennisl
Author: dennisl
Date: Sun Jan  7 05:26:51 2007
New Revision: 493719

URL: http://svn.apache.org/viewvc?view=revrev=493719
Log:
Remove trailing spaces.

Modified:
jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample
jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample

Modified: jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample?view=diffrev=493719r1=493718r2=493719
==
--- jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample (original)
+++ jakarta/commons/proper/commons-build/trunk/samples/pom.xml.sample Sun Jan  
7 05:26:51 2007
@@ -16,7 +16,7 @@
 AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
-under the License.
+under the License.
 --
 
 project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;

Modified: 
jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample?view=diffrev=493719r1=493718r2=493719
==
--- jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample 
(original)
+++ jakarta/commons/proper/commons-build/trunk/samples/sandbox-pom.xml.sample 
Sun Jan  7 05:26:51 2007
@@ -16,7 +16,7 @@
 AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
-under the License.
+under the License.
 --
 
 project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-jaxme development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-jaxme has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 34 runs.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jaxme :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-jaxme-07012007.jar] identifier set to 
project name
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-js on: Maven on 
Project:commons-jelly-tags-jaxme
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme on: Maven on 
Project:commons-jelly-tags-jaxme
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on 
Project:commons-jelly-tags-jaxme
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-xs on: Maven on 
Project:commons-jelly-tags-jaxme
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 1807012007, vmgump.apache.org:vmgump-public:1807012007
Gump E-mail Identifier (unique within run) #39.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-jaxme development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-jaxme has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 34 runs.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jaxme :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-jaxme-07012007.jar] identifier set to 
project name
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- No such project [ws-jaxme] for property.
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-js on: Maven on 
Project:commons-jelly-tags-jaxme
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme on: Maven on 
Project:commons-jelly-tags-jaxme
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on 
Project:commons-jelly-tags-jaxme
 -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme]
 -ERROR- Unhandled Property: maven.jar.jaxme-xs on: Maven on 
Project:commons-jelly-tags-jaxme
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 1807012007, vmgump.apache.org:vmgump-public:1807012007
Gump E-mail Identifier (unique within run) #39.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493725 - /jakarta/commons/proper/commons-parent/trunk/pom.xml

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 06:22:50 2007
New Revision: 493725

URL: http://svn.apache.org/viewvc?view=revrev=493725
Log:
Remove Commons prefix from manifest entires and add default source/target 
compiler properties

Modified:
jakarta/commons/proper/commons-parent/trunk/pom.xml

Modified: jakarta/commons/proper/commons-parent/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/pom.xml?view=diffrev=493725r1=493724r2=493725
==
--- jakarta/commons/proper/commons-parent/trunk/pom.xml (original)
+++ jakarta/commons/proper/commons-parent/trunk/pom.xml Sun Jan  7 06:22:50 2007
@@ -110,10 +110,10 @@
 configuration
   archive
 manifestEntries
-  Specification-TitleCommons 
${project.name}/Specification-Title
+  Specification-Title${project.name}/Specification-Title
   Specification-Version${project.version}/Specification-Version
   
Specification-Vendor${project.organization.name}/Specification-Vendor
-  Implementation-TitleCommons 
${project.name}/Implementation-Title
+  Implementation-Title${project.name}/Implementation-Title
   
Implementation-Version${project.version}/Implementation-Version
   
Implementation-Vendor${project.organization.name}/Implementation-Vendor
   Implementation-Vendor-Idorg.apache/Implementation-Vendor-Id
@@ -261,18 +261,18 @@
 /profile
   /profiles
 
-  !-- Example configuration for compiler source and target JVM --
-  !--
   properties
+
+!-- Default configuration for compiler source and target JVM --
 maven.compile.source1.3/maven.compile.source
 maven.compile.target1.3/maven.compile.target
-  /properties 
-  --
-  properties
+
 !--
   Make the deployment protocol pluggable. This allows to switch to
   other protocols like scpexe, which some users prefer over scp.
 --
 commons.deployment.protocolscp/commons.deployment.protocol
+
   /properties
+
 /project



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (LANG-312) DateFormatUtils.format with Timezone parameter CET produces wrong date in summer time 1945 to 1949

2007-01-07 Thread Dennis Lundberg (JIRA)

[ 
https://issues.apache.org/jira/browse/LANG-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462828
 ] 

Dennis Lundberg commented on LANG-312:
--

The test case fail for me on Windows XP using Sun's JDK 1.4.2_13 and 1.5.0_09.
I did some simple debugging and printed out the underlying int for both the 
Calendar and Date objects. Here are the results:

Running org.apache.commons.lang.time.TimeTestSuite
Cal = -684841660985
Date = -6849

I also printed out the expected pattern and the String created by 
SimpleDateFormat:

19/04/1948 != 18/04/1948

 DateFormatUtils.format with Timezone parameter CET produces wrong date in 
 summer time 1945 to 1949
 

 Key: LANG-312
 URL: https://issues.apache.org/jira/browse/LANG-312
 Project: Commons Lang
  Issue Type: Improvement
Affects Versions: 2.1, 2.2
 Environment: IBM Java 1.4.2, Sun Java 1.4.2, Windows XP, SuSE Linux 
 Enterprise 9, German systems, at winter time
Reporter: Hayo
 Fix For: 3.0


 DateFormatUtils.format(dt, dd/MM/, Timezone.getTimezone(CET), 
 Locale.GERMANY); returns the date of the day before during summer time of the 
 years 1945 to 1949. The problem was detected on a system running in 
 Locale.GERMANY, current time CET, JDK 1.4.2.
 The problem does not occur with the call DateFormatUtils.format(dt, 
 dd/MM/); which presumably uses the system defaults. These are likely to 
 be the same as the parameters i have passed.
 The following code snippet demonstrates the problem:
 for (int year = 0; year  150; year ++) {
 for (int month = 0; month = 11; month ++) {
 for (int day = 1; day = 28; day ++) {
 java.sql.Date dt = new java.sql.Date(year, month, day); 
 // or java.util.Date
 String def = DateFormatUtils.format(dt, dd/MM/);
 String cet = DateFormatUtils.format(dt, dd/MM/, 
 Timezone.getTimezone(CET), Locale.GERMANY);
 
 if (!cet.equals(def)) {
 System.err.println(dt.toLocaleString() +  Default:  
 + def +  CET:  + cet);
 }
 }
 } 
 }
 
 Output:
 --
 
 03.04.1945 00:00:00 Default: 03/04/1945 CET:02/04/1945
 [...]
 18.11.1945 00:00:00 Default: 18/11/1945 CET:17/11/1945
 15.04.1946 00:00:00 Default: 15/04/1946 CET:14/04/1946
 [...]
 07.10.1946 00:00:00 Default: 07/10/1946 CET:06/10/1946
 07.04.1947 00:00:00 Default: 07/04/1947 CET:06/04/1947
 [...]
 05.10.1947 00:00:00 Default: 05/10/1947 CET:04/10/1947
 19.04.1948 00:00:00 Default: 19/04/1948 CET:18/04/1948
 [...]
 03.10.1948 00:00:00 Default: 03/10/1948 CET:02/10/1948
 11.04.1949 00:00:00 Default: 11/04/1949 CET:10/04/1949
 [...]
 02.10.1949 00:00:00 Default: 02/10/1949 CET:01/10/1949
 This seems to be during the summer time of 1949 to 1945 in Berlin, and only 
 in Berlin. Setting the Locale to any other value has no effect on that. So i 
 ask myself, what results other central european users get. Setting the 
 Timezone to GMT+2 extracts exactly the high summer times in 1945 and 1947 
 (MEHSZ). (See below for list of summer times).
 I could guess that some calendar calculations work with different libraries 
 that have different summer time maps (java.util.Date vs. Calendar). This 
 might depend on my environment, so this task should be tested by others (with 
 their local Timezone).
 The API documentation does not clearly state what effect the Timezone/Locale 
 parameters should have.
 In my strong opinion at least dates passed as java.sql.Date should not be 
 normalized to summer/standard time. A date is a date! For java.util.Date the 
 date recalculation behaviour should be mentioned in the docs, if it is really 
 intended this way by design.
 ===
 These where the actual summer times in Germany 
 (http://www.ptb.de/de/org/4/44/441/salt.htm 
  
 http://de.wikipedia.org/wiki/Hochsommerzeit#Mitteleurop.C3.A4ische_Sommerzeit)
 a) Summer time, Advance to CET (GMT+1): 1 hour (GMT+2)
 1916-04-30   23:00:00 CET   until 1916-10-01  1:00:00 CEST
 1917-04-162:00:00 CET   until 1917-09-17  3:00:00 CEST
 1918-04-152:00:00 CET   until 1918-09-16  3:00:00 CEST
 1919 until 1939: No Summer time
 1940-04-012:00:00 CET   until 1942-11-02  3:00:00 CEST
 1943-03-292:00:00 CET   until 1943-10-04  3:00:00 CEST
 1944-04-032:00:00 CET   until 1944-10-02  3:00:00 CEST
 1945-04-022:00:00 CET   until 1945-09-16  2:00:00 CEST
 Special: Berlin and sowjet occupied zone:
 (1945-05-24)  2:00:00 CET   until 1945-11-18  

Re: [nightly build] betwixt finder failed.

2007-01-07 Thread Phil Steitz

On 1/7/07, Dennis Lundberg [EMAIL PROTECTED] wrote:


[EMAIL PROTECTED] wrote:
 Failed build logs:
 http://people.apache.org/~psteitz/commons-nightlies/20070107/betwixt.log
 http://people.apache.org/~psteitz/commons-nightlies/20070107/finder.log

The Maven 2 installation running the nightly builds needs to upgrade its
jar-plugin to version 2.1, otherwise Phil's changes to the parent pom
will cause this failure for finder or other M2 builds.



What is the best way to do that?  Wouldn't it be best to put the explicit
versioned dependency in the pom(s) that need it?  I don't like having builds
depend on local setups. I guess if its maven itself that  needs to be
upgraded we can doc that somewhere and do it, but if its a plugin, we
learned the hard way with m1 that its best to specify these in the poms.

Also, what changes to the parent are you talking about?

Thanks for looking into this.

Phil

--

Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-jsl development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 16 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-07012007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-07012007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66)
[junit] at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at 

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-jsl development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 16 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-07012007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-07012007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66)
[junit] at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at 

[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-fmt development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-fmt-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-fmt-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html
Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 13 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-07012007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-07012007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-07012007.jar
-
[junit] at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
[junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
[junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
[junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
[junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[junit] at 
org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)

[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) failed

2007-01-07 Thread commons-jelly-tags-fmt development
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-fmt-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-fmt-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html
Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 13 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-07012007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-07012007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-07012007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-07012007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-07012007.jar
-
[junit] at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
[junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
[junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
[junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
[junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[junit] at 
org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)

Re: [all] jarfiles in svn

2007-01-07 Thread Martin Cooper

On 1/7/07, Joerg Heinicke [EMAIL PROTECTED] wrote:


Simon Kitching skitching at apache.org writes:

 For a start, if every project were to do this, the impact on the
 Apache SVN repository would be huge.

Cocoon (maintenance branch 2.1) has currently 111 jars with about 40 MB in
its
repository (+ the one for the environment [2]), we are regularly upgrading
them
and it has never been seen as a problem from infrastructure team.

 I would instead prefer to see ant builds using get to download jars as
 needed. The maven repositories can be used as a convenient source for
 the jars, eg

http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/build.xml

I posted my opinion on this recently [3]:
In general I don't like the need for internet access on build time.



This is a red herring. One way or another, you're going to have to get the
jars from the network, whether it's getting them from SVN, or having Maven
or Ant retrieve them. And in all of those three cases, once you have them on
your local machine, you don't need the network to build the next time.

--
Martin Cooper


But with Ant

it's at least better than with Maven as the build environment itself does
not
get changed.

My concerns are raised after one year mess with Maven in Cocoon trunk.

Regards
Jörg

[1] http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/lib/
[2] http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/tools/lib/
[3]
http://marc.theaimsgroup.com/?l=jakarta-commons-devm=116811395603150w=4


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [all] jarfiles in svn

2007-01-07 Thread Joerg Heinicke
Martin Cooper martinc at apache.org writes:

  In general I don't like the need for internet access on build time.
 
 This is a red herring. One way or another, you're going to have to get the
 jars from the network, whether it's getting them from SVN, or having Maven
 or Ant retrieve them. And in all of those three cases, once you have them on
 your local machine, you don't need the network to build the next time.

There is one big difference: With everything in the src jar or at least in the
svn checkout your requirements are less sophisticated than with the build
system. For src jar I only need a browser, for svn checkout I need a svn client,
but for Ant and Maven I need additionally Java and the build environment itself.
And this is a big difference if the machine with internet access is not your
local machine.

(I speak from experience. In my company I get access to the internet only via a
terminal server. There is no build environment. For proposed changes in the
build I need to download all dependencies by hand.)

Regards
Jörg


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [all] jarfiles in svn

2007-01-07 Thread Matt Benson
--- Martin Cooper [EMAIL PROTECTED] wrote:
[SNIP]
 This is a red herring. One way or another, you're
 going to have to get the
 jars from the network, whether it's getting them
 from SVN, or having Maven
 or Ant retrieve them. And in all of those three
 cases, once you have them on
 your local machine, you don't need the network to
 build the next time.
 

Fairly recently in Ant we switched our build to
dynamically obtain (if necessary) the maven2 ant tasks
to get our optional dependencies for full builds. 
Steve Loughran put it together initially; I later
refined (IMHO) it.  ;)  I actually extracted it all
into a single Ant buildfile (fetch.xml) with the
intent of using it in commons-openpgp (again, I never
got around to actually doing it), but if/when my
committer status goes through I could adapt jxpath to
use this means of optionally obtaining dependencies
and see how it goes over.

-Matt

 --
 Martin Cooper
 
 
 But with Ant
  it's at least better than with Maven as the build
 environment itself does
  not
  get changed.
 
  My concerns are raised after one year mess with
 Maven in Cocoon trunk.
 
  Regards
  Jörg
 
  [1]

http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/lib/
  [2]

http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/tools/lib/
  [3]
 

http://marc.theaimsgroup.com/?l=jakarta-commons-devm=116811395603150w=4
 
 
 

-
  To unsubscribe, e-mail:
 [EMAIL PROTECTED]
  For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493795 - in /jakarta/commons/proper/betwixt/trunk: src/java/org/apache/commons/betwixt/ src/java/org/apache/commons/betwixt/digester/ xdocs/

2007-01-07 Thread rdonkin
Author: rdonkin
Date: Sun Jan  7 10:30:56 2007
New Revision: 493795

URL: http://svn.apache.org/viewvc?view=revrev=493795
Log:
Added switch to force introspector to use context classloader. Fix for 
BETWIXT-57.

Modified:

jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/IntrospectionConfiguration.java

jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/XMLIntrospector.java

jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ClassRule.java

jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ElementRule.java

jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/MappedPropertyRule.java

jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/RuleSupport.java
jakarta/commons/proper/betwixt/trunk/xdocs/tasks.xml

Modified: 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/IntrospectionConfiguration.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/IntrospectionConfiguration.java?view=diffrev=493795r1=493794r2=493795
==
--- 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/IntrospectionConfiguration.java
 (original)
+++ 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/IntrospectionConfiguration.java
 Sun Jan  7 10:30:56 2007
@@ -111,6 +111,11 @@
 */
private PropertySuppressionStrategy propertySuppressionStrategy = 
PropertySuppressionStrategy.DEFAULT;

+/**
+ * Should the introspector use the context classloader.
+ */
+private boolean useContextClassLoader = false;
+
 /**
   * Gets the codeClassNormalizer/code strategy.
   * This is used to determine the Class to be introspected
@@ -491,5 +496,24 @@
 public void setElementSuppressionStrategy(
 ElementSuppressionStrategy elementSuppressionStrategy) {
 this.elementSuppressionStrategy = elementSuppressionStrategy;
+}
+
+/**
+ * Should be context classloader be used when loading classes?
+ * @return codetrue/code if the context classloader is to be used 
during introspection, 
+ * codefalse/code otherwise
+ */
+public boolean isUseContextClassLoader() {
+return useContextClassLoader;
+}
+
+/**
+ * Sets whether the context classloader should be used to load classes 
during introspection.
+ * For containers with well behaved context classloaders,
+ * this should typically be set to true.
+ * @param useContextClassLoader
+ */
+public void setUseContextClassLoader(boolean useContextClassLoader) {
+this.useContextClassLoader = useContextClassLoader;
 }
 }

Modified: 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/XMLIntrospector.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/XMLIntrospector.java?view=diffrev=493795r1=493794r2=493795
==
--- 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/XMLIntrospector.java
 (original)
+++ 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/XMLIntrospector.java
 Sun Jan  7 10:30:56 2007
@@ -1244,6 +1244,7 @@
 digester = new XMLBeanInfoDigester();
 digester.setXMLIntrospector( this );
 }
+
digester.setUseContextClassLoader(configuration.isUseContextClassLoader());
 digester.setBeanClass( aClass );
 }
 

Modified: 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ClassRule.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ClassRule.java?view=diffrev=493795r1=493794r2=493795
==
--- 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ClassRule.java
 (original)
+++ 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ClassRule.java
 Sun Jan  7 10:30:56 2007
@@ -54,7 +54,7 @@
 
 try {
 
-Class beanClass = Class.forName(className);
+Class beanClass = loadClass(className);
 XMLBeanInfo xmlBeanInfo = new XMLBeanInfo(beanClass);
 XMLBeanInfoDigester xmlBeanInfoDigester = (XMLBeanInfoDigester) 
getDigester();
 xmlBeanInfoDigester.setBeanClass(beanClass);

Modified: 
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/digester/ElementRule.java
URL: 

[jira] Commented: (BETWIXT-57) Class loader problem in JBoss version 4.0.4GA

2007-01-07 Thread Robert Burrell Donkin (JIRA)

[ 
https://issues.apache.org/jira/browse/BETWIXT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462843
 ] 

Robert Burrell Donkin commented on BETWIXT-57:
--

There are issues with switching universally to using the context classloader: 
too many containers do not set this classloader correctly. Digester rules 
should use the classloader provided by Digester. So, the Betwixt rules should 
use the Digester classloader. However, the Digester implemetation is not 
exposed by XmlIntrospector. So, this setting needs to be added into the 
IntrospectionConfiguration.

I've committed these changes into trunk.

Now, when using Betwixt in a container like JBoss with a well behaved context 
classloader, setUseContextClassLoader(true) should called on 
IntrospectionConfiguration for the XMLIntrospector. This should produce the 
same result as the fix above. Please try the latest code and open this again if 
this fix doesn't work.

 Class loader problem in JBoss version 4.0.4GA
 -

 Key: BETWIXT-57
 URL: https://issues.apache.org/jira/browse/BETWIXT-57
 Project: Commons Betwixt
  Issue Type: Bug
 Environment: JBoss application server version 4.0.4GA. Probably 
 affects most versions of JBoss
Reporter: Surjit Sen
Priority: Critical

 When using betwixt in a JBoss application, Class not found exceptions get 
 thrown when Class.forName methods are called in classes 
 org.apache.commons.betwixt.digester.ElementRule and 
 org.apache.commons.betwixt.digester.ClassRule. Specifically the Class.forName 
 method uses the system class loader to load classes and in JBoss the 
 classpath normally does not contain the application jar files. The fix is 
 very simple. The Class.forName method calls in both the classes were replaced 
 with the following code lines in ElementRule and similar changes were made in 
 ClassRule as well. This fix ensures that the appropriate class loader is used 
 for loading classes and is similar to the fix made in log4j.
 ClassLoader loader = 
 Thread.currentThread().getContextClassLoader();
 if (loader == null) {
   loader = 
 Class.forName(implementationClass).getClassLoader();
 //Class clazz = Class.forName(implementationClass);
 }
 Class clazz = loader.loadClass(implementationClass);
 descriptor.setImplementationClass(clazz);

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Resolved: (BETWIXT-57) Class loader problem in JBoss version 4.0.4GA

2007-01-07 Thread Robert Burrell Donkin (JIRA)

 [ 
https://issues.apache.org/jira/browse/BETWIXT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Burrell Donkin resolved BETWIXT-57.
--

Resolution: Fixed

Fix committed.

 Class loader problem in JBoss version 4.0.4GA
 -

 Key: BETWIXT-57
 URL: https://issues.apache.org/jira/browse/BETWIXT-57
 Project: Commons Betwixt
  Issue Type: Bug
 Environment: JBoss application server version 4.0.4GA. Probably 
 affects most versions of JBoss
Reporter: Surjit Sen
Priority: Critical

 When using betwixt in a JBoss application, Class not found exceptions get 
 thrown when Class.forName methods are called in classes 
 org.apache.commons.betwixt.digester.ElementRule and 
 org.apache.commons.betwixt.digester.ClassRule. Specifically the Class.forName 
 method uses the system class loader to load classes and in JBoss the 
 classpath normally does not contain the application jar files. The fix is 
 very simple. The Class.forName method calls in both the classes were replaced 
 with the following code lines in ElementRule and similar changes were made in 
 ClassRule as well. This fix ensures that the appropriate class loader is used 
 for loading classes and is similar to the fix made in log4j.
 ClassLoader loader = 
 Thread.currentThread().getContextClassLoader();
 if (loader == null) {
   loader = 
 Class.forName(implementationClass).getClassLoader();
 //Class clazz = Class.forName(implementationClass);
 }
 Class clazz = loader.loadClass(implementationClass);
 descriptor.setImplementationClass(clazz);

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (LANG-312) DateFormatUtils.format with Timezone parameter CET produces wrong date in summer time 1945 to 1949

2007-01-07 Thread Henri Yandell (JIRA)

[ 
https://issues.apache.org/jira/browse/LANG-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462845
 ] 

Henri Yandell commented on LANG-312:


What's your machine timezone/locale Dennis?

 DateFormatUtils.format with Timezone parameter CET produces wrong date in 
 summer time 1945 to 1949
 

 Key: LANG-312
 URL: https://issues.apache.org/jira/browse/LANG-312
 Project: Commons Lang
  Issue Type: Improvement
Affects Versions: 2.1, 2.2
 Environment: IBM Java 1.4.2, Sun Java 1.4.2, Windows XP, SuSE Linux 
 Enterprise 9, German systems, at winter time
Reporter: Hayo
 Fix For: 3.0


 DateFormatUtils.format(dt, dd/MM/, Timezone.getTimezone(CET), 
 Locale.GERMANY); returns the date of the day before during summer time of the 
 years 1945 to 1949. The problem was detected on a system running in 
 Locale.GERMANY, current time CET, JDK 1.4.2.
 The problem does not occur with the call DateFormatUtils.format(dt, 
 dd/MM/); which presumably uses the system defaults. These are likely to 
 be the same as the parameters i have passed.
 The following code snippet demonstrates the problem:
 for (int year = 0; year  150; year ++) {
 for (int month = 0; month = 11; month ++) {
 for (int day = 1; day = 28; day ++) {
 java.sql.Date dt = new java.sql.Date(year, month, day); 
 // or java.util.Date
 String def = DateFormatUtils.format(dt, dd/MM/);
 String cet = DateFormatUtils.format(dt, dd/MM/, 
 Timezone.getTimezone(CET), Locale.GERMANY);
 
 if (!cet.equals(def)) {
 System.err.println(dt.toLocaleString() +  Default:  
 + def +  CET:  + cet);
 }
 }
 } 
 }
 
 Output:
 --
 
 03.04.1945 00:00:00 Default: 03/04/1945 CET:02/04/1945
 [...]
 18.11.1945 00:00:00 Default: 18/11/1945 CET:17/11/1945
 15.04.1946 00:00:00 Default: 15/04/1946 CET:14/04/1946
 [...]
 07.10.1946 00:00:00 Default: 07/10/1946 CET:06/10/1946
 07.04.1947 00:00:00 Default: 07/04/1947 CET:06/04/1947
 [...]
 05.10.1947 00:00:00 Default: 05/10/1947 CET:04/10/1947
 19.04.1948 00:00:00 Default: 19/04/1948 CET:18/04/1948
 [...]
 03.10.1948 00:00:00 Default: 03/10/1948 CET:02/10/1948
 11.04.1949 00:00:00 Default: 11/04/1949 CET:10/04/1949
 [...]
 02.10.1949 00:00:00 Default: 02/10/1949 CET:01/10/1949
 This seems to be during the summer time of 1949 to 1945 in Berlin, and only 
 in Berlin. Setting the Locale to any other value has no effect on that. So i 
 ask myself, what results other central european users get. Setting the 
 Timezone to GMT+2 extracts exactly the high summer times in 1945 and 1947 
 (MEHSZ). (See below for list of summer times).
 I could guess that some calendar calculations work with different libraries 
 that have different summer time maps (java.util.Date vs. Calendar). This 
 might depend on my environment, so this task should be tested by others (with 
 their local Timezone).
 The API documentation does not clearly state what effect the Timezone/Locale 
 parameters should have.
 In my strong opinion at least dates passed as java.sql.Date should not be 
 normalized to summer/standard time. A date is a date! For java.util.Date the 
 date recalculation behaviour should be mentioned in the docs, if it is really 
 intended this way by design.
 ===
 These where the actual summer times in Germany 
 (http://www.ptb.de/de/org/4/44/441/salt.htm 
  
 http://de.wikipedia.org/wiki/Hochsommerzeit#Mitteleurop.C3.A4ische_Sommerzeit)
 a) Summer time, Advance to CET (GMT+1): 1 hour (GMT+2)
 1916-04-30   23:00:00 CET   until 1916-10-01  1:00:00 CEST
 1917-04-162:00:00 CET   until 1917-09-17  3:00:00 CEST
 1918-04-152:00:00 CET   until 1918-09-16  3:00:00 CEST
 1919 until 1939: No Summer time
 1940-04-012:00:00 CET   until 1942-11-02  3:00:00 CEST
 1943-03-292:00:00 CET   until 1943-10-04  3:00:00 CEST
 1944-04-032:00:00 CET   until 1944-10-02  3:00:00 CEST
 1945-04-022:00:00 CET   until 1945-09-16  2:00:00 CEST
 Special: Berlin and sowjet occupied zone:
 (1945-05-24)  2:00:00 CET   until 1945-11-18  3:00:00 CEST
 (1945-05-24)  3:00:00 CET   until 1945-09-24  2:00:00 MEHSZ
 1946-04-142:00:00 CET   until 1946-10-07  3:00:00 CEST
 1947-04-063:00:00 CET   until 1947-10-05  3:00:00 CEST
 1948-04-182:00:00 CET   until 1948-10-03  3:00:00 CEST
 1949-04-102:00:00 CET   until 1949-10-02  3:00:00 CEST
 b) High summer 

Re: [nightly build] betwixt finder failed.

2007-01-07 Thread Dennis Lundberg

Phil Steitz wrote:

On 1/7/07, Dennis Lundberg [EMAIL PROTECTED] wrote:


[EMAIL PROTECTED] wrote:
 Failed build logs:
 
http://people.apache.org/~psteitz/commons-nightlies/20070107/betwixt.log

 http://people.apache.org/~psteitz/commons-nightlies/20070107/finder.log

The Maven 2 installation running the nightly builds needs to upgrade its
jar-plugin to version 2.1, otherwise Phil's changes to the parent pom
will cause this failure for finder or other M2 builds.



What is the best way to do that?  Wouldn't it be best to put the explicit
versioned dependency in the pom(s) that need it?  I don't like having 
builds

depend on local setups. I guess if its maven itself that  needs to be
upgraded we can doc that somewhere and do it, but if its a plugin, we
learned the hard way with m1 that its best to specify these in the poms.


Yes I've thought about this some more and I agree that the best thing 
would be to lock down the versions in a parent pom somewhere, preferably 
commons-parent. That way we will have reproducible builds no matter runs it.



Also, what changes to the parent are you talking about?


Maven-jar-plugin stopped adding Implementation-* and Specification-* 
stuff in the manifest by default starting with version 2.1. You're 
probably using that new version locally and have not noticed anything. 
The log says there is a duplicate Implementation-Title.




Thanks for looking into this.

Phil

--

Dennis Lundberg




--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (LANG-312) DateFormatUtils.format with Timezone parameter CET produces wrong date in summer time 1945 to 1949

2007-01-07 Thread Dennis Lundberg (JIRA)

[ 
https://issues.apache.org/jira/browse/LANG-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462850
 ] 

Dennis Lundberg commented on LANG-312:
--

I'm in GMT+1 with locale sv_SE.

 DateFormatUtils.format with Timezone parameter CET produces wrong date in 
 summer time 1945 to 1949
 

 Key: LANG-312
 URL: https://issues.apache.org/jira/browse/LANG-312
 Project: Commons Lang
  Issue Type: Improvement
Affects Versions: 2.1, 2.2
 Environment: IBM Java 1.4.2, Sun Java 1.4.2, Windows XP, SuSE Linux 
 Enterprise 9, German systems, at winter time
Reporter: Hayo
 Fix For: 3.0


 DateFormatUtils.format(dt, dd/MM/, Timezone.getTimezone(CET), 
 Locale.GERMANY); returns the date of the day before during summer time of the 
 years 1945 to 1949. The problem was detected on a system running in 
 Locale.GERMANY, current time CET, JDK 1.4.2.
 The problem does not occur with the call DateFormatUtils.format(dt, 
 dd/MM/); which presumably uses the system defaults. These are likely to 
 be the same as the parameters i have passed.
 The following code snippet demonstrates the problem:
 for (int year = 0; year  150; year ++) {
 for (int month = 0; month = 11; month ++) {
 for (int day = 1; day = 28; day ++) {
 java.sql.Date dt = new java.sql.Date(year, month, day); 
 // or java.util.Date
 String def = DateFormatUtils.format(dt, dd/MM/);
 String cet = DateFormatUtils.format(dt, dd/MM/, 
 Timezone.getTimezone(CET), Locale.GERMANY);
 
 if (!cet.equals(def)) {
 System.err.println(dt.toLocaleString() +  Default:  
 + def +  CET:  + cet);
 }
 }
 } 
 }
 
 Output:
 --
 
 03.04.1945 00:00:00 Default: 03/04/1945 CET:02/04/1945
 [...]
 18.11.1945 00:00:00 Default: 18/11/1945 CET:17/11/1945
 15.04.1946 00:00:00 Default: 15/04/1946 CET:14/04/1946
 [...]
 07.10.1946 00:00:00 Default: 07/10/1946 CET:06/10/1946
 07.04.1947 00:00:00 Default: 07/04/1947 CET:06/04/1947
 [...]
 05.10.1947 00:00:00 Default: 05/10/1947 CET:04/10/1947
 19.04.1948 00:00:00 Default: 19/04/1948 CET:18/04/1948
 [...]
 03.10.1948 00:00:00 Default: 03/10/1948 CET:02/10/1948
 11.04.1949 00:00:00 Default: 11/04/1949 CET:10/04/1949
 [...]
 02.10.1949 00:00:00 Default: 02/10/1949 CET:01/10/1949
 This seems to be during the summer time of 1949 to 1945 in Berlin, and only 
 in Berlin. Setting the Locale to any other value has no effect on that. So i 
 ask myself, what results other central european users get. Setting the 
 Timezone to GMT+2 extracts exactly the high summer times in 1945 and 1947 
 (MEHSZ). (See below for list of summer times).
 I could guess that some calendar calculations work with different libraries 
 that have different summer time maps (java.util.Date vs. Calendar). This 
 might depend on my environment, so this task should be tested by others (with 
 their local Timezone).
 The API documentation does not clearly state what effect the Timezone/Locale 
 parameters should have.
 In my strong opinion at least dates passed as java.sql.Date should not be 
 normalized to summer/standard time. A date is a date! For java.util.Date the 
 date recalculation behaviour should be mentioned in the docs, if it is really 
 intended this way by design.
 ===
 These where the actual summer times in Germany 
 (http://www.ptb.de/de/org/4/44/441/salt.htm 
  
 http://de.wikipedia.org/wiki/Hochsommerzeit#Mitteleurop.C3.A4ische_Sommerzeit)
 a) Summer time, Advance to CET (GMT+1): 1 hour (GMT+2)
 1916-04-30   23:00:00 CET   until 1916-10-01  1:00:00 CEST
 1917-04-162:00:00 CET   until 1917-09-17  3:00:00 CEST
 1918-04-152:00:00 CET   until 1918-09-16  3:00:00 CEST
 1919 until 1939: No Summer time
 1940-04-012:00:00 CET   until 1942-11-02  3:00:00 CEST
 1943-03-292:00:00 CET   until 1943-10-04  3:00:00 CEST
 1944-04-032:00:00 CET   until 1944-10-02  3:00:00 CEST
 1945-04-022:00:00 CET   until 1945-09-16  2:00:00 CEST
 Special: Berlin and sowjet occupied zone:
 (1945-05-24)  2:00:00 CET   until 1945-11-18  3:00:00 CEST
 (1945-05-24)  3:00:00 CET   until 1945-09-24  2:00:00 MEHSZ
 1946-04-142:00:00 CET   until 1946-10-07  3:00:00 CEST
 1947-04-063:00:00 CET   until 1947-10-05  3:00:00 CEST
 1948-04-182:00:00 CET   until 1948-10-03  3:00:00 CEST
 1949-04-102:00:00 CET   until 1949-10-02  3:00:00 CEST
 b) High summer time, 

Re: [all] jarfiles in svn

2007-01-07 Thread Simon Kitching
On Sun, 2007-01-07 at 17:08 +, Joerg Heinicke wrote:
 Martin Cooper martinc at apache.org writes:
 
   In general I don't like the need for internet access on build time.
  
  This is a red herring. One way or another, you're going to have to get the
  jars from the network, whether it's getting them from SVN, or having Maven
  or Ant retrieve them. And in all of those three cases, once you have them on
  your local machine, you don't need the network to build the next time.
 
 There is one big difference: With everything in the src jar or at least in the
 svn checkout your requirements are less sophisticated than with the build
 system. For src jar I only need a browser, for svn checkout I need a svn 
 client,
 but for Ant and Maven I need additionally Java and the build environment 
 itself.
 And this is a big difference if the machine with internet access is not your
 local machine.

I've got no objection to commons-transaction providing a custom
download, eg commons-transactions-6.7-src-all.tgz which contains jars
if you feel this would make users happy. However no other commons
project has done this AFAIK, and I don't see any complaints on the user
lists.

When using maven, only the first run needs to download the jars;
thereafter they are cached locally. So, no need for internet access at
build time.

For ant, have a look at the build.xml file in logging that I provided a
link to; it defines a separate getlibs task to download the jars. This
can be run *once* to download the jars, but is not part of the main
build task, so there is no need for internet access at build time.

Re your maven issues: it's not mandatory to use maven to create builds;
ant is fine. Providing both is even better. It's only the jars issue
that is being discussed.


 (I speak from experience. In my company I get access to the internet only via 
 a
 terminal server. There is no build environment. For proposed changes in the
 build I need to download all dependencies by hand.)

A poor corporate internet access policy at one company is *NOT* a good
justification for misusing the Apache SVN repository.

Regards,

Simon


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493881 - /jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

2007-01-07 Thread bayard
Author: bayard
Date: Sun Jan  7 15:50:36 2007
New Revision: 493881

URL: http://svn.apache.org/viewvc?view=revrev=493881
Log:
Votes and comments added. Need to decide how much data should go in the report

Modified:
jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

Modified: jakarta/commons/proper/commons-nightly/trunk/jira-email.vm
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-nightly/trunk/jira-email.vm?view=diffrev=493881r1=493880r2=493881
==
--- jakarta/commons/proper/commons-nightly/trunk/jira-email.vm (original)
+++ jakarta/commons/proper/commons-nightly/trunk/jira-email.vm Sun Jan  7 
15:50:36 2007
@@ -23,6 +23,7 @@
 #set( $projects = $jira.getProjects() )
 ##
 #foreach( $project_key in 
[BEANUTILS,BETWIXT,CHAIN,CLI,CODEC,COLLECTIONS,CONFIGURATION,DAEMON,DBCP,DBUTILS,DIGESTER,EMAIL,FILEUPLOAD,IO,JEXL,JXPATH,LANG,LOGGING,MATH,NET,POOL,SCXML,VALIDATOR,VFS])
+##foreach( $project_key in [JELLY])
 #set( $versions = $jira.getVersions($project_key) )
 #set( $versions = $versions.subtract($versions.equals(id, -1)) )
 #set( $project = $projects.equals(key, $project_key).get(0) )
@@ -38,6 +39,9 @@
 #if( $issues.size() != 0 )
   ${version} - ${resolvedIssues.size()} / ${issues.size()}
 #end
+#foreach( $issue in $issues.greater(votes, 1) )
+[$issue.key] ($issue.votes votes) $issue.summary 
+#end
 #end
 #end
 ##
@@ -46,8 +50,8 @@
 #set( $issues = $issues.equals(resolution, Unresolved) )
   Unversioned - ${issues.size()}
 #foreach( $issue in $issues )
-[$issue.key]  $issue.summary 
-##BUG#$issue.comments.size() comments from 
$issue.comments.unique(username).size() authors
+[$issue.key] ($issue.votes votes) $issue.summary 
+$issue.comments.size() comments from 
$issue.comments.unique(username).size() authors
 #end
 
 #end



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [all] jarfiles in svn

2007-01-07 Thread Phil Steitz

On 1/7/07, Joerg Heinicke [EMAIL PROTECTED] wrote:


Martin Cooper martinc at apache.org writes:

  In general I don't like the need for internet access on build time.

 This is a red herring. One way or another, you're going to have to get
the
 jars from the network, whether it's getting them from SVN, or having
Maven
 or Ant retrieve them. And in all of those three cases, once you have
them on
 your local machine, you don't need the network to build the next time.

There is one big difference: With everything in the src jar or at least in
the
svn checkout your requirements are less sophisticated than with the build
system. For src jar I only need a browser, for svn checkout I need a svn
client,
but for Ant and Maven I need additionally Java and the build environment
itself.
And this is a big difference if the machine with internet access is not
your
local machine.

(I speak from experience. In my company I get access to the internet only
via a
terminal server. There is no build environment. For proposed changes in
the
build I need to download all dependencies by hand.)



I would be more concerned about funny-versioned or unversioned jars coming
in to my environment or builds via svn checkouts.  Most corporate
environments control pretty carefully the external jars used in builds -
both the OSS jars from maven repositories and release distributions.  It
makes things easier if when building from source the dependencies are
explicitly versioned release jars, not whatever happens to be come down with
an svn checkout. The good thing about the great work the Ant, Maven and
repository@ people are doing is that it gets us to standardized jar
distribution.

I know that other apache projects have seen fit to put jars into scm and
they have had lots of reasons to do this - almost always to make builds for
users or release management easier.  Up to now, we have pretty much avoided
this in commons and I for one would really like to keep things that way. I
had never noticed the /lib directory in [transaction] before, though, which
seems to have been there for a couple of years.  Maybe Oliver or someone
else can explain why [transaction] really needs those jars in svn.  I see
the geronimo spec jars were added with the comment that they had been
recompiled for JDK 1.3.  If that is necessary, its probably better to first
ask geronimo to produce *different* artifacts that satisfy this, or at least
to rename these reccompiled artifacts.

Phil


Re: [sandbox] Using commons-skin for all components

2007-01-07 Thread Niall Pemberton

Hi Denis,

Good job on the skin - I added an m2 build to Validator using it and
looks great to me - I've published the m2 generated site for Validator
here:

  http://people.apache.org/~niallp/validator-m2/

I can't see any problems with the skin - but noticed the following
site issues which look like maven plugin features/bugs:

1) Maven changes absolute URLs specified in site.xml to relative URLs.
This isn't a problem for the web sites - but components (like
validator) that include them as docs in the distro it means that the
breadcrumbs (Jakarta and Commons) and links to previous versions
JavaDocs that are only on the site no longer work.

2) The changes report doesn't seem to like content that contains
markup - it seems to split out the markup into a separate report - m1
and m2(x2) changes reports are here for comparison:
 http://jakarta.apache.org/commons/validator/changes-report.html
 http://people.apache.org/~niallp/validator-m2/changes-report.html
(markup removed)
 http://people.apache.org/~niallp/validator-m2/changes.html (removed markup)

3) Validator has a custom issue-tracking page - which seems to cause
the site plugin to omit it from the project information menu and
page:
  http://people.apache.org/~niallp/validator-m2/project-info.html
If I delete the custom version - then m2 generates one and includes it
on both the above.

more comments inline below...

On 1/7/07, Dennis Lundberg [EMAIL PROTECTED] wrote:

Here's a status report on how far I have gotten.

The sandbox parent is finished. I have added a bunch of reports to it
that seems logical, at least to me, for all components. These are:

- Cobertura (test coverage)
- Javadoc
- JXR (cross reference for sources)
- PMD
- Surefire (test results)
- JDepend (metrics)
- Taglist (list things left to do)


One thing I noticed recently with Cobertura is that it includes some
JavaScript files with various (GPL+ other) licenses - maybe we should
switch to JCoverage instead:
   http://tinyurl.com/ynbjge


The individual components have at least the reports they have in their
M1 sites, with these exceptions:


Sounds like a good plan - how will this be handled for proper
components - is commons-parent the right place to put them or do we
need a proper-parent pom?


- i18n is missing JCoverage, but Cobertura does the same thing
- Id and Proxy are missing Clover, but Cobertura does the same thing
- All are missing JavaDoc Report, JavaDoc Warnings Report and Link
check, which does not exist in M2
- All are missing Project License which is available in another place in M2

Some components have their own reports as well. These didn't seem like
something suitable for all components. These reports are:

- Checkstyle (5 component) (requires a configuration file)
- Changelog (3 component)
- Changes (1 component) (requires a changes.xml file)
- FindBugs (1 component)

Still to do:

- I haven't been able to get the logo in the upper right corner to work
simultaneously for M1 and M2. This affects I18n, Id and Proxy.


I fixed this in Validator by copying the logo to site/resources/images
and including a bannerRight element in site.xml


- Id has test failures in M2, which I haven't been able to solve. I
temporarily added a configuration so that the build succeeds even if
there are test failures.
- Id has a downloads page that refers to an M1 report. Need to decide
how to deal with that. Can't have M1 and M2 working at the same time for
this one.


I assume you mean cvs-usage.html? While id is in the sandbox we could
copy the cvs-usage.html to source-repository.html in the maven.xml and
refer to source-repository.html on the downloads page. Once its out of
the sandbox I would remove the downloads page altogether and replace
it with the standard downloads_commons-id.cgi

Alternatively just delete the downloads page now.

Thanks again for doing all this

Niall


- Publish staged sites so that you can all see what it looks like.

Dennis Lundberg wrote:
 Hi

 Before I dive head-first into this I thought I'd ask first. I'd like to
 unify the M2 generated sites for all sandbox components, by making use
 of commons-skin. This would mean:

 1. Make various changes to the sandbox-parent, which is currently
 located in sandbox-trunk:
 - Remove local style rules
 - Remove stuff that is inherited from commons-parent, most notably
 maven-classic-skin

 2. Change pom.xml and site.xml for many sandbox components
 - Make sure inheritance is correct
 - Align navigation structure
 - Remove stuff that is inherited from sandbox-parent

 3. Re-publish the sites for all sandbox components
 - Do mvn site:deploy for all sandbox components
 - Would like to move sandbox-parent to its own directory in SVN
 - If we feel that it's necessary at this time: release commons-skin,
 commons-parent and sandbox-parent


 Does this sound OK to you?

--
Dennis Lundberg


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional 

svn commit: r493940 - /jakarta/commons/proper/fileupload/trunk/pom.xml

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 20:34:30 2007
New Revision: 493940

URL: http://svn.apache.org/viewvc?view=revrev=493940
Log:
Specify maven.compile.source/target properties which removes the need for the 
overriding the compiler plugin configuration. mave jar plugin can also be 
removed once version 2 of the comms-parent pom is released

Modified:
jakarta/commons/proper/fileupload/trunk/pom.xml

Modified: jakarta/commons/proper/fileupload/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/fileupload/trunk/pom.xml?view=diffrev=493940r1=493939r2=493940
==
--- jakarta/commons/proper/fileupload/trunk/pom.xml (original)
+++ jakarta/commons/proper/fileupload/trunk/pom.xml Sun Jan  7 20:34:30 2007
@@ -111,6 +111,10 @@
 
developerConnectionscm:svn:scm:svn:https://svn.apache.org/repos/asf/jakarta/commons/proper/fileupload/trunk/developerConnection
 
urlhttp://svn.apache.org/viewvc/jakarta/commons/proper/fileupload/trunk/url
   /scm
+  properties
+maven.compile.source1.3/maven.compile.source
+maven.compile.target1.3/maven.compile.target
+  /properties 
 
   build
 sourceDirectorysrc/java/sourceDirectory
@@ -126,13 +130,10 @@
   /resource
 /resources
 plugins
-  plugin
-artifactIdmaven-compiler-plugin/artifactId
-configuration
-  source1.3/source
-  target1.3/target
-/configuration
-  /plugin
+  !--
+   TODO: remove the following when commons-parent is released
+ or switch to commons-parent 2-SNAPSHOT version
+   --
   plugin
 artifactIdmaven-jar-plugin/artifactId
 configuration
@@ -140,8 +141,8 @@
 manifestFilesrc/conf/MANIFEST.MF/manifestFile
 manifestEntries
   Specification-Version${project.version}/Specification-Version
-  X-Compile-Source-JDK1.3/X-Compile-Source-JDK
-  X-Compile-Target-JDK1.3/X-Compile-Target-JDK
+  
X-Compile-Source-JDK${maven.compile.source}/X-Compile-Source-JDK
+  
X-Compile-Target-JDK${maven.compile.target}/X-Compile-Target-JDK
 /manifestEntries
   /archive
 /configuration



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493942 - /jakarta/commons/proper/commons-parent/trunk/pom.xml

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 20:39:37 2007
New Revision: 493942

URL: http://svn.apache.org/viewvc?view=revrev=493942
Log:
Use a resource element to include the LICENSE.txt and NOTICE.txt files in the 
jar. The antrun plugin (which was copying in those files) has a bug that causes 
it execute twice if used in both a parent and dependant pom. The only downside 
to using a resource element is that its not inherited if dependant poms also 
specify any resource elements and therefore needs to be duplicated in 
dependant poms in that scenario

Modified:
jakarta/commons/proper/commons-parent/trunk/pom.xml

Modified: jakarta/commons/proper/commons-parent/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/pom.xml?view=diffrev=493942r1=493941r2=493942
==
--- jakarta/commons/proper/commons-parent/trunk/pom.xml (original)
+++ jakarta/commons/proper/commons-parent/trunk/pom.xml Sun Jan  7 20:39:37 2007
@@ -96,6 +96,21 @@
 /mailingList
   /mailingLists
   build
+resources
+  !--
+   N.B. If dependant poms specify resources the following entry will
+need to be added as maven only inherits if no resources are
+specified in the dependant pom.
+   --
+  resource
+directory${basedir}/directory
+targetPathMETA-INF/targetPath
+includes
+  includeLICENSE.txt/include
+  includeNOTICE.txt/include
+/includes
+  /resource
+/resources
 plugins
   !-- TODO: later use toolchain support to do compilation on an external 
JDK 1.3+ compiler --
   plugin
@@ -128,33 +143,6 @@
 configuration
   jdkLevel${maven.compile.source}/jdkLevel
 /configuration
-  /plugin
-  plugin
-!-- This should possibly better be done by using a resource
- definition. However, if we declare a resource with
- ${basedir} as the base directory, then the
- maven-source-plugin will add the whole directory to
- its contents.
---
-artifactIdmaven-antrun-plugin/artifactId
-executions
-  execution
-phasegenerate-resources/phase
-configuration
-  tasks
-copy todir=${project.build.outputDirectory}/META-INF
-  fileset dir=${basedir}
-include name=LICENSE.txt /
-include name=NOTICE.txt /
-  /fileset
-/copy
-  /tasks
-/configuration
-goals
-  goalrun/goal
-/goals
-  /execution
-/executions
   /plugin
 /plugins
   /build



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493948 - /jakarta/commons/sandbox/i18n/trunk/pom.xml

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 20:52:09 2007
New Revision: 493948

URL: http://svn.apache.org/viewvc?view=revrev=493948
Log:
Add resource element

Modified:
jakarta/commons/sandbox/i18n/trunk/pom.xml

Modified: jakarta/commons/sandbox/i18n/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/sandbox/i18n/trunk/pom.xml?view=diffrev=493948r1=493947r2=493948
==
--- jakarta/commons/sandbox/i18n/trunk/pom.xml (original)
+++ jakarta/commons/sandbox/i18n/trunk/pom.xml Sun Jan  7 20:52:09 2007
@@ -54,6 +54,14 @@
 testSourceDirectorysrc/test/testSourceDirectory
 resources
   resource
+directory${basedir}/directory
+targetPathMETA-INF/targetPath
+includes
+  includeLICENSE.txt/include
+  includeNOTICE.txt/include
+/includes
+  /resource
+  resource
 directory${basedir}/src/resources/directory
   /resource
 /resources
@@ -103,10 +111,6 @@
   /dependencies
   reporting
 plugins
-  plugin
-groupIdorg.apache.maven.plugins/groupId
-artifactIdmaven-changelog-plugin/artifactId
-  /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-changes-plugin/artifactId



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Add Matt Benson as a Jakarta committer

2007-01-07 Thread Stefan Bodewig
On Fri, 5 Jan 2007, Henri Yandell [EMAIL PROTECTED] wrote:
 As you can see on the list, Matt would like to help out with JXPath.

+1

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493955 - /jakarta/commons/proper/io/trunk/build.xml

2007-01-07 Thread bayard
Author: bayard
Date: Sun Jan  7 21:26:33 2007
New Revision: 493955

URL: http://svn.apache.org/viewvc?view=revrev=493955
Log:
Changed the src-ide.zip to sources.jar and added a javadoc.jar

Modified:
jakarta/commons/proper/io/trunk/build.xml

Modified: jakarta/commons/proper/io/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/build.xml?view=diffrev=493955r1=493954r2=493955
==
--- jakarta/commons/proper/io/trunk/build.xml (original)
+++ jakarta/commons/proper/io/trunk/build.xml Sun Jan  7 21:26:33 2007
@@ -103,7 +103,7 @@
 copy todir=${srcdir}/META-INF
   fileset dir=${basedir} includes=LICENSE*, NOTICE* /
 /copy
-jar jarfile=${defaulttargetdir}/${final.name}-src-ide.zip 
basedir=${srcdir} /
+jar jarfile=${defaulttargetdir}/${final.name}-sources.jar 
basedir=${srcdir} manifest=${basedir}/src/conf/MANIFEST.MF/
 antcall target=internal-md5
   param name=path value=${defaulttargetdir}/${final.name}.jar/
 /antcall
@@ -123,6 +123,8 @@
 !-- but the javadoc is built on JDK1.4 --
 mkdir dir=${dist.bin} /
 mkdir dir=${dist.zip.dir} /
+!-- Javadoc --
+jar jarfile=${defaulttargetdir}/${final.name}-javadoc.jar 
basedir=${javadocdir} manifest=${basedir}/src/conf/MANIFEST.MF/
!-- Binary --
 copy todir=${dist.bin}
   fileset dir=${defaulttargetdir} includes=*.jar,*.zip /
@@ -312,4 +314,4 @@
 /clirr
   /target
 
-/project
\ No newline at end of file
+/project



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493957 - in /jakarta/commons/proper/validator/trunk: LICENSE.txt NOTICE.txt build.xml maven.xml pom.xml project.xml src/main/assembly/bin.xml src/main/assembly/src.xml src/main/resources/

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 21:36:12 2007
New Revision: 493957

URL: http://svn.apache.org/viewvc?view=revrev=493957
Log:
Move LICENSE.txt and NOTICE.txt back to the root directory

Added:
jakarta/commons/proper/validator/trunk/LICENSE.txt
  - copied unchanged from r493950, 
jakarta/commons/proper/validator/trunk/src/main/resources/LICENSE.txt
jakarta/commons/proper/validator/trunk/NOTICE.txt
  - copied unchanged from r493950, 
jakarta/commons/proper/validator/trunk/src/main/resources/NOTICE.txt
Removed:
jakarta/commons/proper/validator/trunk/src/main/resources/LICENSE.txt
jakarta/commons/proper/validator/trunk/src/main/resources/NOTICE.txt
Modified:
jakarta/commons/proper/validator/trunk/build.xml
jakarta/commons/proper/validator/trunk/maven.xml
jakarta/commons/proper/validator/trunk/pom.xml
jakarta/commons/proper/validator/trunk/project.xml
jakarta/commons/proper/validator/trunk/src/main/assembly/bin.xml
jakarta/commons/proper/validator/trunk/src/main/assembly/src.xml

Modified: jakarta/commons/proper/validator/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/validator/trunk/build.xml?view=diffrev=493957r1=493956r2=493957
==
--- jakarta/commons/proper/validator/trunk/build.xml (original)
+++ jakarta/commons/proper/validator/trunk/build.xml Sun Jan  7 21:36:12 2007
@@ -315,16 +315,16 @@
 property name=final.name 
value=commons-${component.name}-${component.version}/
 /ant
 
-copy  file=${resources.home}/LICENSE.txt
+copy  file=LICENSE.txt
   todir=${dist.home}/
-copy  file=${resources.home}/NOTICE.txt
+copy  file=NOTICE.txt
   todir=${dist.home}/
 copy  file=RELEASE-NOTES.txt
   todir=${dist.home}/
 mkdir  dir=${build.home}/classes/META-INF/
-copy  file=${resources.home}/LICENSE.txt
+copy  file=LICENSE.txt
  tofile=${build.home}/classes/META-INF/LICENSE.txt/
-copy  file=${resources.home}/NOTICE.txt
+copy  file=NOTICE.txt
  tofile=${build.home}/classes/META-INF/NOTICE.txt/
 
 manifest file=${build.home}/MANIFEST.MF

Modified: jakarta/commons/proper/validator/trunk/maven.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/validator/trunk/maven.xml?view=diffrev=493957r1=493956r2=493957
==
--- jakarta/commons/proper/validator/trunk/maven.xml (original)
+++ jakarta/commons/proper/validator/trunk/maven.xml Sun Jan  7 21:36:12 2007
@@ -24,13 +24,6 @@
 attainGoal name=html2xdoc/
   /preGoal
 
-  preGoal name=site
-!-- keep site generation  checkstyle happy --
-copy todir=${basedir}
-  fileset file=${basedir}/src/main/resources/LICENSE.txt/
-/copy
-  /preGoal
-
   postGoal name=java:compile
 
 copy todir=${maven.build.dir}/classes/
@@ -62,8 +55,7 @@
 
 !-- Copy the NOTICE --
 copy todir=${maven.dist.bin.assembly.dir}
-  fileset file=${basedir}/src/main/resources/LICENSE.txt/
-  fileset file=${basedir}/src/main/resources/NOTICE.txt/
+  fileset file=${basedir}/NOTICE.txt/
   fileset file=${basedir}/RELEASE-NOTES.txt/
   fileset file=${maven.build.dir}/*.js/
 /copy
@@ -77,8 +69,7 @@
 
 !-- Copy the NOTICE --
 copy todir=${maven.dist.src.assembly.dir}
-  fileset file=${basedir}/src/main/resources/LICENSE.txt/
-  fileset file='${basedir}/src/main/resources/NOTICE.txt'/
+  fileset file=${basedir}/NOTICE.txt/
   fileset file=${basedir}/RELEASE-NOTES.txt/
   fileset file=${basedir}/build.properties.sample/
 /copy

Modified: jakarta/commons/proper/validator/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/validator/trunk/pom.xml?view=diffrev=493957r1=493956r2=493957
==
--- jakarta/commons/proper/validator/trunk/pom.xml (original)
+++ jakarta/commons/proper/validator/trunk/pom.xml Sun Jan  7 21:36:12 2007
@@ -112,6 +112,14 @@
 build
 resources
 resource
+directory${basedir}/directory
+targetPathMETA-INF/targetPath
+includes
+includeLICENSE.txt/include
+includeNOTICE.txt/include
+/includes
+/resource
+resource
 directorysrc/main/resources/directory
 /resource
 resource
@@ -222,6 +230,7 @@
 artifactIdmaven-checkstyle-plugin/artifactId
 configuration
 configLocationcheckstyle.xml/configLocation
+enableRulesSummaryfalse/enableRulesSummary
 /configuration
 /plugin
 

Modified: jakarta/commons/proper/validator/trunk/project.xml
URL: 

svn commit: r493958 - /jakarta/commons/proper/validator/trunk/pom.xml

2007-01-07 Thread niallp
Author: niallp
Date: Sun Jan  7 21:39:42 2007
New Revision: 493958

URL: http://svn.apache.org/viewvc?view=revrev=493958
Log:
remove unnecessary parameters

Modified:
jakarta/commons/proper/validator/trunk/pom.xml

Modified: jakarta/commons/proper/validator/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/validator/trunk/pom.xml?view=diffrev=493958r1=493957r2=493958
==
--- jakarta/commons/proper/validator/trunk/pom.xml (original)
+++ jakarta/commons/proper/validator/trunk/pom.xml Sun Jan  7 21:39:42 2007
@@ -138,8 +138,6 @@
 configuration
 tasks
 ant antfile=build-javascript.xml 
target=compress
-property name=proj  
value=${project.directory}/
-property name=base  value=${basedir}/
 property name=build.dir  
value=${project.build.directory}/
 property name=output.dir 
value=${project.build.outputDirectory}/
 property name=final.name 
value=${project.build.finalName}/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493966 - in /jakarta/commons/proper/io/trunk: build.xml pom.xml project.xml

2007-01-07 Thread bayard
Author: bayard
Date: Sun Jan  7 22:46:20 2007
New Revision: 493966

URL: http://svn.apache.org/viewvc?view=revrev=493966
Log:
Setting version to 1.3

Modified:
jakarta/commons/proper/io/trunk/build.xml
jakarta/commons/proper/io/trunk/pom.xml
jakarta/commons/proper/io/trunk/project.xml

Modified: jakarta/commons/proper/io/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/build.xml?view=diffrev=493966r1=493965r2=493966
==
--- jakarta/commons/proper/io/trunk/build.xml (original)
+++ jakarta/commons/proper/io/trunk/build.xml Sun Jan  7 22:46:20 2007
@@ -26,7 +26,7 @@
   /property
   property name=testreportdir value=${basedir}/build/test-reports
   /property
-  property name=final.name value=commons-io-1.3-SNAPSHOT /
+  property name=final.name value=commons-io-1.3 /
   property name=dist.build.dir value=${basedir}/build/dist-build /
   property name=dist.bin value=${dist.build.dir}/${final.name} /
   property name=dist.src value=${dist.build.dir}/${final.name}-src /

Modified: jakarta/commons/proper/io/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/pom.xml?view=diffrev=493966r1=493965r2=493966
==
--- jakarta/commons/proper/io/trunk/pom.xml (original)
+++ jakarta/commons/proper/io/trunk/pom.xml Sun Jan  7 22:46:20 2007
@@ -27,7 +27,7 @@
   modelVersion4.0.0/modelVersion
   groupIdcommons-io/groupId
   artifactIdcommons-io/artifactId
-  version1.3-SNAPSHOT/version
+  version1.3/version
   nameIO/name
 
   inceptionYear2002/inceptionYear

Modified: jakarta/commons/proper/io/trunk/project.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/project.xml?view=diffrev=493966r1=493965r2=493966
==
--- jakarta/commons/proper/io/trunk/project.xml (original)
+++ jakarta/commons/proper/io/trunk/project.xml Sun Jan  7 22:46:20 2007
@@ -21,7 +21,7 @@
   nameIO/name
   groupIdcommons-io/groupId
   artifactIdcommons-io/artifactId
-  currentVersion1.3-SNAPSHOT/currentVersion
+  currentVersion1.3/currentVersion
   inceptionYear2002/inceptionYear
   shortDescriptionCommons IO/shortDescription
   description



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493967 - in /jakarta/commons/proper/io/trunk/xdocs: building.xml index.xml navigation.xml upgradeto1_3.xml

2007-01-07 Thread bayard
Author: bayard
Date: Sun Jan  7 23:02:24 2007
New Revision: 493967

URL: http://svn.apache.org/viewvc?view=revrev=493967
Log:
Preparing for a 1.3 release candidate

Added:
jakarta/commons/proper/io/trunk/xdocs/upgradeto1_3.xml   (with props)
Modified:
jakarta/commons/proper/io/trunk/xdocs/building.xml
jakarta/commons/proper/io/trunk/xdocs/index.xml
jakarta/commons/proper/io/trunk/xdocs/navigation.xml

Modified: jakarta/commons/proper/io/trunk/xdocs/building.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/xdocs/building.xml?view=diffrev=493967r1=493966r2=493967
==
--- jakarta/commons/proper/io/trunk/xdocs/building.xml (original)
+++ jakarta/commons/proper/io/trunk/xdocs/building.xml Sun Jan  7 23:02:24 2007
@@ -29,6 +29,7 @@
 /p
 p
   You may also be interested in the upgrade notes:br /
+  Upgrade a href=upgradeto1_3.htmlfrom 1.2 to 1.3/abr /
   Upgrade a href=upgradeto1_2.htmlfrom 1.1 to 1.2/abr /
   Upgrade a href=upgradeto1_1.htmlfrom 1.0 to 1.1/abr /
 /p

Modified: jakarta/commons/proper/io/trunk/xdocs/index.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/xdocs/index.xml?view=diffrev=493967r1=493966r2=493967
==
--- jakarta/commons/proper/io/trunk/xdocs/index.xml (original)
+++ jakarta/commons/proper/io/trunk/xdocs/index.xml Sun Jan  7 23:02:24 2007
@@ -46,7 +46,8 @@
 The JavaDoc API documents are available online:
 /p
 ul
-liThe a href=api-release/index.htmlcurrent release 1.2/a/li
+liThe a href=api-release/index.htmlcurrent release 1.3/a/li
+liThe a href=api-1.2/index.htmlprevious version 1.2/a/li
 liThe a href=api-1.1/index.htmlprevious version 1.1/a/li
 liThe a href=apidocs/index.htmllatest SVN/a/li
 /ul
@@ -58,9 +59,9 @@
 !-- == --
 section name=Releases
 p
-The latest version is v1.2. - 
+The latest version is v1.3. - 
 a 
href=http://jakarta.apache.org/site/downloads/downloads_commons-io.cgi;Download
 now!/abr /
-The a href=upgradeto1_2.htmlupgrade notes/a are also available.
+The a href=upgradeto1_3.htmlupgrade notes/a are also available.
 
 /p
 p

Modified: jakarta/commons/proper/io/trunk/xdocs/navigation.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/xdocs/navigation.xml?view=diffrev=493967r1=493966r2=493967
==
--- jakarta/commons/proper/io/trunk/xdocs/navigation.xml (original)
+++ jakarta/commons/proper/io/trunk/xdocs/navigation.xml Sun Jan  7 23:02:24 
2007
@@ -15,7 +15,7 @@
   item name=User guide href=/description.html/
   item name=Best practices href=/bestpractices.html/
   !--item name=History href=/history.html/--
-  item name=Javadoc (1.2 release) href=api-release/index.html/
+  item name=Javadoc (1.3 release) href=api-release/index.html/
 /menu
 
 menu name=Development

Added: jakarta/commons/proper/io/trunk/xdocs/upgradeto1_3.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/xdocs/upgradeto1_3.xml?view=autorev=493967
==
--- jakarta/commons/proper/io/trunk/xdocs/upgradeto1_3.xml (added)
+++ jakarta/commons/proper/io/trunk/xdocs/upgradeto1_3.xml Sun Jan  7 23:02:24 
2007
@@ -0,0 +1,228 @@
+?xml version=1.0?
+!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the License); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an AS IS BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+--
+document
+ properties
+  titleUpgrade from 1.2 to 1.3/title
+  author email=commons-dev@jakarta.apache.orgCommons Documentation 
Team/author
+ /properties
+body
+
+section name=Upgrade
+p
+These are the release notes and advice for upgrading Commons-IO from
+version 1.2 to version 1.3.
+source
+Commons IO is a package of Java utility classes for java.io's hierarchy.  
+Classes in this package are considered to be so standard and of such high 
+reuse as to justify existence in java.io.
+
+Commons IO contains utility classes, stream implementations, file filters, 
+and endian transformation classes.
+
+
+Compatibility with 1.2
+--
+Binary compatible - Yes
+
+Source compatible - Yes
+
+Semantic compatible - Yes
+  Check 

svn commit: r493970 - /jakarta/commons/proper/io/tags/IO_1_3_RC1/

2007-01-07 Thread bayard
Author: bayard
Date: Sun Jan  7 23:12:40 2007
New Revision: 493970

URL: http://svn.apache.org/viewvc?view=revrev=493970
Log:
Tagging 1.3-rc1

Added:
jakarta/commons/proper/io/tags/IO_1_3_RC1/
  - copied from r493969, jakarta/commons/proper/io/trunk/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r493971 - in /jakarta/commons/proper/io/trunk: build.xml pom.xml project.xml

2007-01-07 Thread bayard
Author: bayard
Date: Sun Jan  7 23:13:16 2007
New Revision: 493971

URL: http://svn.apache.org/viewvc?view=revrev=493971
Log:
Moving back to 1.3-SNAPSHOT to avoid any surprises

Modified:
jakarta/commons/proper/io/trunk/build.xml
jakarta/commons/proper/io/trunk/pom.xml
jakarta/commons/proper/io/trunk/project.xml

Modified: jakarta/commons/proper/io/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/build.xml?view=diffrev=493971r1=493970r2=493971
==
--- jakarta/commons/proper/io/trunk/build.xml (original)
+++ jakarta/commons/proper/io/trunk/build.xml Sun Jan  7 23:13:16 2007
@@ -26,7 +26,7 @@
   /property
   property name=testreportdir value=${basedir}/build/test-reports
   /property
-  property name=final.name value=commons-io-1.3 /
+  property name=final.name value=commons-io-1.3-SNAPSHOT /
   property name=dist.build.dir value=${basedir}/build/dist-build /
   property name=dist.bin value=${dist.build.dir}/${final.name} /
   property name=dist.src value=${dist.build.dir}/${final.name}-src /

Modified: jakarta/commons/proper/io/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/pom.xml?view=diffrev=493971r1=493970r2=493971
==
--- jakarta/commons/proper/io/trunk/pom.xml (original)
+++ jakarta/commons/proper/io/trunk/pom.xml Sun Jan  7 23:13:16 2007
@@ -27,7 +27,7 @@
   modelVersion4.0.0/modelVersion
   groupIdcommons-io/groupId
   artifactIdcommons-io/artifactId
-  version1.3/version
+  version1.3-SNAPSHOT/version
   nameIO/name
 
   inceptionYear2002/inceptionYear

Modified: jakarta/commons/proper/io/trunk/project.xml
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/io/trunk/project.xml?view=diffrev=493971r1=493970r2=493971
==
--- jakarta/commons/proper/io/trunk/project.xml (original)
+++ jakarta/commons/proper/io/trunk/project.xml Sun Jan  7 23:13:16 2007
@@ -21,7 +21,7 @@
   nameIO/name
   groupIdcommons-io/groupId
   artifactIdcommons-io/artifactId
-  currentVersion1.3/currentVersion
+  currentVersion1.3-SNAPSHOT/currentVersion
   inceptionYear2002/inceptionYear
   shortDescriptionCommons IO/shortDescription
   description



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[VOTE] IO 1.3 RC1

2007-01-07 Thread Henri Yandell

I've made a first release candidate of IO 1.3, tagged IO_1_3_RC1.

Available at:

http://people.apache.org/~bayard/commons-io/1.3-rc1/

Various build files, clirr/jardiff reports and the proposed site.

[ ] +1
[ ] -1

Vote to end on Friday (if it makes it that far).

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] IO 1.3 RC1

2007-01-07 Thread Niall Pemberton

Everything looks good except the source distro doesn't build -
FileFilterTestCase fails because it checks for STATUS.html in
testFiles() - but STATUS.html isn't included in the source distro.

Niall

On 1/8/07, Henri Yandell [EMAIL PROTECTED] wrote:

I've made a first release candidate of IO 1.3, tagged IO_1_3_RC1.

Available at:

http://people.apache.org/~bayard/commons-io/1.3-rc1/

Various build files, clirr/jardiff reports and the proposed site.

[ ] +1
[ ] -1

Vote to end on Friday (if it makes it that far).

Hen


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]