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

2008-04-12 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 3 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-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-11042008.jar] identifier set to 
project name
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-js.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-xs.
 -DEBUG- Dependency on packaged-jaxme exists, no need to add for property 
maven.jar.jaxme-api.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html
Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build)
Work ended in a state of : Failed
Elapsed: 11 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme]
CLASSPATH: 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-11042008.jar:/srv/gump/public/workspace/apache-commons/collections/build/commons-collections-11042008.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-11042008.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-11042008.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-11042008.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-11042008.jar:/srv/gump/public/workspace/apache-commons/jexl/dist/commons-jexl-11042008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-11042008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-11042008.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/jaxen/target/jaxen-11042008.jar:/srv/gump/
 
packages/ws-jaxme-0.5/lib/jaxme2-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmeapi-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmejs-0.5.jar:/srv/gump/packages/ws-jaxme-0.5/lib/jaxmexs-0.5.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xmlunit/build/lib/xmlunit-11042008.jar
-
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac]   super.characters(pChars, pOffset, pLen);
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305:
 cannot find symbol
[javac] symbol  : variable super
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] super.init(pData);
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler
[javac] __handler_Name.init(getData());
[javac] ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22:
 cannot find symbol
[javac] symbol  : method getData()
[javac] location: class 
org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler

Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread Niall Pemberton
On Sat, Apr 12, 2008 at 1:25 PM, sebb [EMAIL PROTECTED] wrote:
 On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   The Sling project has requested an OSGi enabled release of Commons
Collections and since it seems unlikely that Collections 3.3 will be
ready in the timescale they require, I have created a release
candidate for Collections 3.2.1. This is basically a re-packaging of
the Collections 3.2 release with the appropriate OSGi meta data in the
Collections jar. The only changes I have made to the java source code
is to modify source file license headers to conform to current policy
and remove tab characters. An m2 build has been added to the
Collections 3.2 branch I created and the site has been updated to
reflect the 3.2.1 release.
  
The artifacts are here:
http://people.apache.org/~niallp/collections-3.2.1-rc1/

  All look OK, and source zip agrees with SVN tag.


SVN Tag:

 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/
  
Site:
http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
(note m2 generates relative links, so some don't work - but the site
is for info and not included in the release artifacts)
  
Release Notes:
http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html
  
RAT Report:

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html
  
CLIRR Report:
Clirr failed and so is not available
  

  That's very unfortunate ... seems like the problem may be due to a
  doubly-nested class?

Yes I googled this and saw others having the same problem, but
couldn't find a solution.

RC2 has been built with m2 -

  Since the build says it is targetted at 1.2, building with Java 1.5 is
  not ideal.
  Building with 1.2 would be a pain, but using 1.3 should be easy enough.

  I just tried, and Ant test is OK with Java 1.3.1 and Ant 1.6.5

  However, Maven1.0.2 with Java 1.3.1 gives some test failures, e.g.:

  Testsuite: org.apache.commons.collections.TestAllPackages
  Tests run: 13009, Failures: 0, Errors: 109, Time elapsed: 16.359 sec
  These are mainly java.lang.NoSuchMethodError failures.

  If I run TestAllPackages in Ant, it works fine.
  Perhaps a bug in Maven1?

Looks that way. I had the same problem, but as you say since the tests
pass on Ant with JDK 1.3 I didn't think it was a big issue.

  And using Java 1.2 with Ant 1.6.5 I get:

 [javac] 
 C:\ReleaseCheck\commons-collections-3.2.1-src\src\java\org\apache\commons\collections\buffer\BoundedBuffer.java:188:
  Var
  iable lock in class
  org.apache.commons.collections.collection.SynchronizedCollection not
  accessible from inner class org.apache.comm
  ons.collections.buffer.BoundedBuffer. NotifyingIterator.

 [javac] synchronized (lock) {

  Maybe it's time to drop 1.2 support?

Probably for Collections 1.3, but I wanted to create this release with
the same options as the original 3.2 release.

   but m1 and ant builds are available - details here:
http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html

  The Ant test runs a different set of tests from M1 and M2 - I
  calculate that it runs 12957 tests, instead of 13009. Perhaps the Ant
  script should default to TestAllPackages as well?

  Two sections both headed Ant Goals - perhaps they could be combined
  for the actual site release? Also the page says that the default build
  is Ant - so why release using M2?

Because the m2 build uses the bundle plugin which puts the OSGi meta
data in automatically and is the whole point of this release.

Niall

Vote is open for 72 hours
  
Thanks in advance for your feedback/votes.
  
Niall

 -
  
[  ] +1  I support this release
[  ] +0  I am OK with this release
[  ] -0   OK, but
[  ] -1   I do not support this release
  
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
  
  

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



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



Re: svn commit: r647000 - in /commons/proper/io/trunk/src: java/org/apache/commons/io/FileUtils.java test/org/apache/commons/io/FileUtilsTestCase.java

2008-04-12 Thread Niall Pemberton
On Sat, Apr 12, 2008 at 10:22 AM, Stephen Colebourne
[EMAIL PROTECTED] wrote:
 I believe that this is a Java 1.4 specific method. Are we OK with that?

Yes the current trunk requires a minimum of JDK 1.5

Niall

  Stephen


  [EMAIL PROTECTED] wrote:

  -urls[i] = files[i].toURL();
  +urls[i] = files[i].toURI().toURL();
 

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



Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread sebb
On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 On Sat, Apr 12, 2008 at 1:25 PM, sebb [EMAIL PROTECTED] wrote:
   On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 The Sling project has requested an OSGi enabled release of Commons
  Collections and since it seems unlikely that Collections 3.3 will be
  ready in the timescale they require, I have created a release
  candidate for Collections 3.2.1. This is basically a re-packaging of
  the Collections 3.2 release with the appropriate OSGi meta data in the
  Collections jar. The only changes I have made to the java source code
  is to modify source file license headers to conform to current policy
  and remove tab characters. An m2 build has been added to the
  Collections 3.2 branch I created and the site has been updated to
  reflect the 3.2.1 release.

  The artifacts are here:
  http://people.apache.org/~niallp/collections-3.2.1-rc1/
  
All look OK, and source zip agrees with SVN tag.
  
  
  SVN Tag:
  
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/

  Site:
  http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
  (note m2 generates relative links, so some don't work - but the site
  is for info and not included in the release artifacts)

  Release Notes:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html

  RAT Report:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html

  CLIRR Report:
  Clirr failed and so is not available

  
That's very unfortunate ... seems like the problem may be due to a
doubly-nested class?


 Yes I googled this and saw others having the same problem, but
  couldn't find a solution.


Found the solution - see:
https://sourceforge.net/tracker/index.php?func=detailaid=1022446group_id=89627atid=590799
last e-mail on the page.

After I dropped the DoubleOrderedMap$1$* classes from 3.2.1, clirr ran
OK - it gave:

INFO: 7003: org.apache.commons.collections.map.AbstractHashedMap$HashIterator:
Method 'public java.lang.Object next()' has been removed, but an
inherited definition exists.
INFO: 7003: org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
Method 'public java.lang.Object next()' has been removed, but an
inherited definition exists.
INFO: 7003: org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
Method 'public java.lang.Object previous()' has been removed, but an
inherited definition exists.

The 3.2 jar does not contain these $1$* class names, presumably
because an older compiler was used.


  RC2 has been built with m2 -
  
Since the build says it is targetted at 1.2, building with Java 1.5 is
not ideal.
Building with 1.2 would be a pain, but using 1.3 should be easy enough.
  
I just tried, and Ant test is OK with Java 1.3.1 and Ant 1.6.5
  
However, Maven1.0.2 with Java 1.3.1 gives some test failures, e.g.:
  
Testsuite: org.apache.commons.collections.TestAllPackages
Tests run: 13009, Failures: 0, Errors: 109, Time elapsed: 16.359 sec
These are mainly java.lang.NoSuchMethodError failures.
  
If I run TestAllPackages in Ant, it works fine.
Perhaps a bug in Maven1?


 Looks that way. I had the same problem, but as you say since the tests
  pass on Ant with JDK 1.3 I didn't think it was a big issue.


I also tested the pre-built jar using Java 1.3.1 and Ant 1.6.5 -
TestAllPackages completed OK.

So I agree, it should be OK.


And using Java 1.2 with Ant 1.6.5 I get:
  
   [javac] 
 C:\ReleaseCheck\commons-collections-3.2.1-src\src\java\org\apache\commons\collections\buffer\BoundedBuffer.java:188:
Var
iable lock in class
org.apache.commons.collections.collection.SynchronizedCollection not
accessible from inner class org.apache.comm
ons.collections.buffer.BoundedBuffer. NotifyingIterator.
  
   [javac] synchronized (lock) {
  
Maybe it's time to drop 1.2 support?


 Probably for Collections 1.3, but I wanted to create this release with
  the same options as the original 3.2 release.


 but m1 and ant builds are available - details here:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html
  
The Ant test runs a different set of tests from M1 and M2 - I
calculate that it runs 12957 tests, instead of 13009. Perhaps the Ant
script should default to TestAllPackages as well?
  
Two sections both headed Ant Goals - perhaps they could be combined
for the actual site release? Also the page says that the default build
is Ant - so why release using M2?


 Because the m2 build uses the bundle plugin which puts the OSGi meta
  data in automatically and is the whole point of this release.

Might have been better to use the minimum 

Re: [configuration] New hierarchical configurations

2008-04-12 Thread Oliver Heger
Emmanuel Bourg wrote:
 Oliver Heger a écrit :
 
 XMLConfiguration and XMLPropertiesConfiguration remain in the main
 package. 

 Why?
 
 
 The purpose of the package is to group only the SAX readers as they form
 a hierarchy providing a specific feature, just like the BeanUtils bridge
 in the beanutils package. I don't know if these classes are frequently
 used, actually I don't know the use cases for these readers. As a non
 core feature I don't think they deserve to remain in the main package.
 
 I don't think moving the XMLConfiguration and XMLPropertiesConfiguration
 classes in an xml package is necessary, I don't have any problem with
 them staying in the main package. Also, that would not make sense to
 move them but not XMLPropertyListConfiguration in the plist package, and
 having XMLPropertyListConfiguration outside the plist package seems
 absurds too.
 
 Emmanuel Bourg
 
The main reason for the restructuring of the packages was to increase
modularity, which is especially important in environments like OSGi
where you have fine control over the packages to import. An all
configurations in the main package approach won't help here.

Oliver

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



Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread Niall Pemberton
On Sat, Apr 12, 2008 at 2:18 PM, sebb [EMAIL PROTECTED] wrote:

 On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   On Sat, Apr 12, 2008 at 1:25 PM, sebb [EMAIL PROTECTED] wrote:
 On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   The Sling project has requested an OSGi enabled release of Commons
Collections and since it seems unlikely that Collections 3.3 will be
ready in the timescale they require, I have created a release
candidate for Collections 3.2.1. This is basically a re-packaging of
the Collections 3.2 release with the appropriate OSGi meta data in 
 the
Collections jar. The only changes I have made to the java source 
 code
is to modify source file license headers to conform to current 
 policy
and remove tab characters. An m2 build has been added to the
Collections 3.2 branch I created and the site has been updated to
reflect the 3.2.1 release.
  
The artifacts are here:
http://people.apache.org/~niallp/collections-3.2.1-rc1/

  All look OK, and source zip agrees with SVN tag.


SVN Tag:

 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/
  
Site:
http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
(note m2 generates relative links, so some don't work - but the site
is for info and not included in the release artifacts)
  
Release Notes:

 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html
  
RAT Report:

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html
  
CLIRR Report:
Clirr failed and so is not available
  

  That's very unfortunate ... seems like the problem may be due to a
  doubly-nested class?
  
  
   Yes I googled this and saw others having the same problem, but
couldn't find a solution.
  

  Found the solution - see:
  
 https://sourceforge.net/tracker/index.php?func=detailaid=1022446group_id=89627atid=590799
  last e-mail on the page.

Its sort of a solution, but I wouldn't want to hack the jar around as
part of the release process.

  After I dropped the DoubleOrderedMap$1$* classes from 3.2.1, clirr ran
  OK - it gave:

Thanks for doing that :)

  INFO: 7003: 
 org.apache.commons.collections.map.AbstractHashedMap$HashIterator:
  Method 'public java.lang.Object next()' has been removed, but an
  inherited definition exists.
  INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
  Method 'public java.lang.Object next()' has been removed, but an
  inherited definition exists.
  INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
  Method 'public java.lang.Object previous()' has been removed, but an
  inherited definition exists.

  The 3.2 jar does not contain these $1$* class names, presumably
  because an older compiler was used.


  
RC2 has been built with m2 -

  Since the build says it is targetted at 1.2, building with Java 1.5 is
  not ideal.
  Building with 1.2 would be a pain, but using 1.3 should be easy enough.

  I just tried, and Ant test is OK with Java 1.3.1 and Ant 1.6.5

  However, Maven1.0.2 with Java 1.3.1 gives some test failures, e.g.:

  Testsuite: org.apache.commons.collections.TestAllPackages
  Tests run: 13009, Failures: 0, Errors: 109, Time elapsed: 16.359 sec
  These are mainly java.lang.NoSuchMethodError failures.

  If I run TestAllPackages in Ant, it works fine.
  Perhaps a bug in Maven1?
  
  
   Looks that way. I had the same problem, but as you say since the tests
pass on Ant with JDK 1.3 I didn't think it was a big issue.
  

  I also tested the pre-built jar using Java 1.3.1 and Ant 1.6.5 -
  TestAllPackages completed OK.

  So I agree, it should be OK.


  
  And using Java 1.2 with Ant 1.6.5 I get:

 [javac] 
 C:\ReleaseCheck\commons-collections-3.2.1-src\src\java\org\apache\commons\collections\buffer\BoundedBuffer.java:188:
  Var
  iable lock in class
  org.apache.commons.collections.collection.SynchronizedCollection not
  accessible from inner class org.apache.comm
  ons.collections.buffer.BoundedBuffer. NotifyingIterator.

 [javac] synchronized (lock) {

  Maybe it's time to drop 1.2 support?
  
  
   Probably for Collections 1.3, but I wanted to create this release with
the same options as the original 3.2 release.
  
  
   but m1 and ant builds are available - details here:

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html

  The Ant test runs a different set of tests from M1 and M2 - I
  calculate that it runs 12957 tests, instead of 13009. Perhaps the 

Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread sebb
On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 On Sat, Apr 12, 2008 at 2:18 PM, sebb [EMAIL PROTECTED] wrote:
  
   On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 On Sat, Apr 12, 2008 at 1:25 PM, sebb [EMAIL PROTECTED] wrote:
   On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 The Sling project has requested an OSGi enabled release of Commons
  Collections and since it seems unlikely that Collections 3.3 
 will be
  ready in the timescale they require, I have created a release
  candidate for Collections 3.2.1. This is basically a 
 re-packaging of
  the Collections 3.2 release with the appropriate OSGi meta data 
 in the
  Collections jar. The only changes I have made to the java source 
 code
  is to modify source file license headers to conform to current 
 policy
  and remove tab characters. An m2 build has been added to the
  Collections 3.2 branch I created and the site has been updated to
  reflect the 3.2.1 release.

  The artifacts are here:
  http://people.apache.org/~niallp/collections-3.2.1-rc1/
  
All look OK, and source zip agrees with SVN tag.
  
  
  SVN Tag:
  
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/

  Site:
  http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
  (note m2 generates relative links, so some don't work - but the 
 site
  is for info and not included in the release artifacts)

  Release Notes:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html

  RAT Report:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html

  CLIRR Report:
  Clirr failed and so is not available

  
That's very unfortunate ... seems like the problem may be due to a
doubly-nested class?


 Yes I googled this and saw others having the same problem, but
  couldn't find a solution.

  
Found the solution - see:

 https://sourceforge.net/tracker/index.php?func=detailaid=1022446group_id=89627atid=590799
last e-mail on the page.


 Its sort of a solution, but I wouldn't want to hack the jar around as
  part of the release process.


After I dropped the DoubleOrderedMap$1$* classes from 3.2.1, clirr ran
OK - it gave:


 Thanks for doing that :)


INFO: 7003: 
 org.apache.commons.collections.map.AbstractHashedMap$HashIterator:
Method 'public java.lang.Object next()' has been removed, but an
inherited definition exists.
INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
Method 'public java.lang.Object next()' has been removed, but an
inherited definition exists.
INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
Method 'public java.lang.Object previous()' has been removed, but an
inherited definition exists.
  
The 3.2 jar does not contain these $1$* class names, presumably
because an older compiler was used.
  
  

  RC2 has been built with m2 -
  
Since the build says it is targetted at 1.2, building with Java 1.5 
 is
not ideal.
Building with 1.2 would be a pain, but using 1.3 should be easy 
 enough.
  
I just tried, and Ant test is OK with Java 1.3.1 and Ant 1.6.5
  
However, Maven1.0.2 with Java 1.3.1 gives some test failures, e.g.:
  
Testsuite: org.apache.commons.collections.TestAllPackages
Tests run: 13009, Failures: 0, Errors: 109, Time elapsed: 16.359 sec
These are mainly java.lang.NoSuchMethodError failures.
  
If I run TestAllPackages in Ant, it works fine.
Perhaps a bug in Maven1?


 Looks that way. I had the same problem, but as you say since the tests
  pass on Ant with JDK 1.3 I didn't think it was a big issue.

  
I also tested the pre-built jar using Java 1.3.1 and Ant 1.6.5 -
TestAllPackages completed OK.
  
So I agree, it should be OK.
  
  

And using Java 1.2 with Ant 1.6.5 I get:
  
   [javac] 
 C:\ReleaseCheck\commons-collections-3.2.1-src\src\java\org\apache\commons\collections\buffer\BoundedBuffer.java:188:
Var
iable lock in class
org.apache.commons.collections.collection.SynchronizedCollection not
accessible from inner class org.apache.comm
ons.collections.buffer.BoundedBuffer. NotifyingIterator.
  
   [javac] synchronized (lock) {
  
Maybe it's time to drop 1.2 support?


 Probably for Collections 1.3, but I wanted to create this release with
  the same options as the original 3.2 

Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread Niall Pemberton
On Sat, Apr 12, 2008 at 4:21 PM, sebb [EMAIL PROTECTED] wrote:

 On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   On Sat, Apr 12, 2008 at 2:18 PM, sebb [EMAIL PROTECTED] wrote:

 On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   On Sat, Apr 12, 2008 at 1:25 PM, sebb [EMAIL PROTECTED] wrote:
 On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   The Sling project has requested an OSGi enabled release of 
 Commons
Collections and since it seems unlikely that Collections 3.3 
 will be
ready in the timescale they require, I have created a release
candidate for Collections 3.2.1. This is basically a 
 re-packaging of
the Collections 3.2 release with the appropriate OSGi meta 
 data in the
Collections jar. The only changes I have made to the java 
 source code
is to modify source file license headers to conform to 
 current policy
and remove tab characters. An m2 build has been added to the
Collections 3.2 branch I created and the site has been 
 updated to
reflect the 3.2.1 release.
  
The artifacts are here:
http://people.apache.org/~niallp/collections-3.2.1-rc1/

  All look OK, and source zip agrees with SVN tag.


SVN Tag:

 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/
  
Site:
http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
(note m2 generates relative links, so some don't work - but 
 the site
is for info and not included in the release artifacts)
  
Release Notes:

 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html
  
RAT Report:

 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html
  
CLIRR Report:
Clirr failed and so is not available
  

  That's very unfortunate ... seems like the problem may be due to 
 a
  doubly-nested class?
  
  
   Yes I googled this and saw others having the same problem, but
couldn't find a solution.
  

  Found the solution - see:
  
 https://sourceforge.net/tracker/index.php?func=detailaid=1022446group_id=89627atid=590799
  last e-mail on the page.
  
  
   Its sort of a solution, but I wouldn't want to hack the jar around as
part of the release process.
  
  
  After I dropped the DoubleOrderedMap$1$* classes from 3.2.1, clirr ran
  OK - it gave:
  
  
   Thanks for doing that :)
  
  
  INFO: 7003: 
 org.apache.commons.collections.map.AbstractHashedMap$HashIterator:
  Method 'public java.lang.Object next()' has been removed, but an
  inherited definition exists.
  INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
  Method 'public java.lang.Object next()' has been removed, but an
  inherited definition exists.
  INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
  Method 'public java.lang.Object previous()' has been removed, but an
  inherited definition exists.

  The 3.2 jar does not contain these $1$* class names, presumably
  because an older compiler was used.


  
RC2 has been built with m2 -

  Since the build says it is targetted at 1.2, building with Java 
 1.5 is
  not ideal.
  Building with 1.2 would be a pain, but using 1.3 should be easy 
 enough.

  I just tried, and Ant test is OK with Java 1.3.1 and Ant 1.6.5

  However, Maven1.0.2 with Java 1.3.1 gives some test failures, 
 e.g.:

  Testsuite: org.apache.commons.collections.TestAllPackages
  Tests run: 13009, Failures: 0, Errors: 109, Time elapsed: 16.359 
 sec
  These are mainly java.lang.NoSuchMethodError failures.

  If I run TestAllPackages in Ant, it works fine.
  Perhaps a bug in Maven1?
  
  
   Looks that way. I had the same problem, but as you say since the 
 tests
pass on Ant with JDK 1.3 I didn't think it was a big issue.
  

  I also tested the pre-built jar using Java 1.3.1 and Ant 1.6.5 -
  TestAllPackages completed OK.

  So I agree, it should be OK.


  
  And using Java 1.2 with Ant 1.6.5 I get:

 [javac] 
 C:\ReleaseCheck\commons-collections-3.2.1-src\src\java\org\apache\commons\collections\buffer\BoundedBuffer.java:188:
  Var
  iable lock in class
  org.apache.commons.collections.collection.SynchronizedCollection 
 not
  accessible from inner class org.apache.comm

Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread Oliver Heger
+1

Artifacts look good.

On the site I found that the Javadoc (3.2.1 release) link in the main
menue does not work, but I assume it will when the site is deployed.

Oliver

Niall Pemberton wrote:
 The Sling project has requested an OSGi enabled release of Commons
 Collections and since it seems unlikely that Collections 3.3 will be
 ready in the timescale they require, I have created a release
 candidate for Collections 3.2.1. This is basically a re-packaging of
 the Collections 3.2 release with the appropriate OSGi meta data in the
 Collections jar. The only changes I have made to the java source code
 is to modify source file license headers to conform to current policy
 and remove tab characters. An m2 build has been added to the
 Collections 3.2 branch I created and the site has been updated to
 reflect the 3.2.1 release.
 
 The artifacts are here:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/
 
 SVN Tag:
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/
 
 Site:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
 (note m2 generates relative links, so some don't work - but the site
 is for info and not included in the release artifacts)
 
 Release Notes:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html
 
 RAT Report:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html
 
 CLIRR Report:
 Clirr failed and so is not available
 
 RC2 has been built with m2 - but m1 and ant builds are available - details 
 here:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html
 
 Vote is open for 72 hours
 
 Thanks in advance for your feedback/votes.
 
 Niall
 -
 
 [  ] +1  I support this release
 [  ] +0  I am OK with this release
 [  ] -0   OK, but
 [  ] -1   I do not support this release
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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



Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread sebb
On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 On Sat, Apr 12, 2008 at 4:21 PM, sebb [EMAIL PROTECTED] wrote:
  
   On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 On Sat, Apr 12, 2008 at 2:18 PM, sebb [EMAIL PROTECTED] wrote:
  
   On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 On Sat, Apr 12, 2008 at 1:25 PM, sebb [EMAIL PROTECTED] wrote:
   On 12/04/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 The Sling project has requested an OSGi enabled release of 
 Commons
  Collections and since it seems unlikely that Collections 
 3.3 will be
  ready in the timescale they require, I have created a 
 release
  candidate for Collections 3.2.1. This is basically a 
 re-packaging of
  the Collections 3.2 release with the appropriate OSGi meta 
 data in the
  Collections jar. The only changes I have made to the java 
 source code
  is to modify source file license headers to conform to 
 current policy
  and remove tab characters. An m2 build has been added to 
 the
  Collections 3.2 branch I created and the site has been 
 updated to
  reflect the 3.2.1 release.

  The artifacts are here:
  http://people.apache.org/~niallp/collections-3.2.1-rc1/
  
All look OK, and source zip agrees with SVN tag.
  
  
  SVN Tag:
  
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/

  Site:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
  (note m2 generates relative links, so some don't work - 
 but the site
  is for info and not included in the release artifacts)

  Release Notes:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html

  RAT Report:
  
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html

  CLIRR Report:
  Clirr failed and so is not available

  
That's very unfortunate ... seems like the problem may be due 
 to a
doubly-nested class?


 Yes I googled this and saw others having the same problem, but
  couldn't find a solution.

  
Found the solution - see:

 https://sourceforge.net/tracker/index.php?func=detailaid=1022446group_id=89627atid=590799
last e-mail on the page.


 Its sort of a solution, but I wouldn't want to hack the jar around as
  part of the release process.


After I dropped the DoubleOrderedMap$1$* classes from 3.2.1, clirr 
 ran
OK - it gave:


 Thanks for doing that :)


INFO: 7003: 
 org.apache.commons.collections.map.AbstractHashedMap$HashIterator:
Method 'public java.lang.Object next()' has been removed, but an
inherited definition exists.
INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
Method 'public java.lang.Object next()' has been removed, but an
inherited definition exists.
INFO: 7003: 
 org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator:
Method 'public java.lang.Object previous()' has been removed, but an
inherited definition exists.
  
The 3.2 jar does not contain these $1$* class names, presumably
because an older compiler was used.
  
  

  RC2 has been built with m2 -
  
Since the build says it is targetted at 1.2, building with 
 Java 1.5 is
not ideal.
Building with 1.2 would be a pain, but using 1.3 should be 
 easy enough.
  
I just tried, and Ant test is OK with Java 1.3.1 and Ant 1.6.5
  
However, Maven1.0.2 with Java 1.3.1 gives some test failures, 
 e.g.:
  
Testsuite: org.apache.commons.collections.TestAllPackages
Tests run: 13009, Failures: 0, Errors: 109, Time elapsed: 
 16.359 sec
These are mainly java.lang.NoSuchMethodError failures.
  
If I run TestAllPackages in Ant, it works fine.
Perhaps a bug in Maven1?


 Looks that way. I had the same problem, but as you say since the 
 tests
  pass on Ant with JDK 1.3 I didn't think it was a big issue.

  
I also tested the pre-built jar using Java 1.3.1 and Ant 1.6.5 -
TestAllPackages completed OK.
  
So I agree, it should be OK.
  
  

And using Java 1.2 with Ant 1.6.5 I get:
  
   [javac] 
 

Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread sebb
+1

BTW a check of SVN recommended:

svn ps svn:eol-style native
COLLECTIONS_3_2_1_RC1/src/test/org/apache/commons/collections/map/TestMultiValueMap.java

S///
On 12/04/2008, Oliver Heger [EMAIL PROTECTED] wrote:
 +1

  Artifacts look good.

  On the site I found that the Javadoc (3.2.1 release) link in the main
  menue does not work, but I assume it will when the site is deployed.


  Oliver


  Niall Pemberton wrote:
   The Sling project has requested an OSGi enabled release of Commons
   Collections and since it seems unlikely that Collections 3.3 will be
   ready in the timescale they require, I have created a release
   candidate for Collections 3.2.1. This is basically a re-packaging of
   the Collections 3.2 release with the appropriate OSGi meta data in the
   Collections jar. The only changes I have made to the java source code
   is to modify source file license headers to conform to current policy
   and remove tab characters. An m2 build has been added to the
   Collections 3.2 branch I created and the site has been updated to
   reflect the 3.2.1 release.
  
   The artifacts are here:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/
  
   SVN Tag:
   
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/
  
   Site:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
   (note m2 generates relative links, so some don't work - but the site
   is for info and not included in the release artifacts)
  
   Release Notes:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
   
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html
  
   RAT Report:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html
  
   CLIRR Report:
   Clirr failed and so is not available
  
   RC2 has been built with m2 - but m1 and ant builds are available - details 
 here:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html
  
   Vote is open for 72 hours
  
   Thanks in advance for your feedback/votes.
  
   Niall
   
 -
  
   [  ] +1  I support this release
   [  ] +0  I am OK with this release
   [  ] -0   OK, but
   [  ] -1   I do not support this release
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  


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



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



Re: [all] jakarta still appearing in Reply-to header

2008-04-12 Thread Luc Maisonobe

sebb wrote:

On 06/03/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Hello,

  It seems that the Reply-to header for commons list still contains a 
reference to
  Jakarta. I first thought my client badly rewrote this, but now I 
think the
  header is already set up like this from the beginning. For the dev 
list, it

  reads:
 Reply-To: Jakarta Commons Developers List dev@commons.apache.org
  I think the user list has a similar setting.

  Do you see the same header and if so how can this be fixed ?

Yes, I see the same header.

I think the change can probably be made by a list moderator, or else
someone with infrastructure/apmail karma will need to get involved.

I have open an issue in JIRA for this.
http://issues.apache.org/jira/browse/INFRA-1582

Luc


  Luc


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



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






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



[continuum] BUILD FAILURE: Commons Exec (Sandbox)

2008-04-12 Thread Continuum VMBuild Server

Online report : 
http://vmbuild.apache.org/continuum/buildResult.action?buildId=76278projectId=178

Build statistics:
 State: Failed
 Previous State: Ok
 Started at: Sat 12 Apr 2008 15:30:37 -0700
 Finished at: Sat 12 Apr 2008 15:31:56 -0700
 Total time: 1m 18s
 Build Trigger: Schedule
 Build Number: 30
 Exit code: 1
 Building machine hostname: vmbuild.apache.org
 Operating system : Linux(unknown)
 Java Home version : 
 java version 1.5.0_12

 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
 Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
   
 Builder version :

 Maven version: 2.0.7
 Java version: 1.5.0_12
 OS name: linux version: 2.6.20-16-server arch: i386
   


SCM Changes:

Changed: niallp @ Sat 12 Apr 2008 14:51:39 -0700
Comment: Add assembly descriptors
Files changed:
 /commons/sandbox/exec/trunk/pom.xml ( 647500 )
 /commons/sandbox/exec/trunk/src/assembly ( 647500 )
 /commons/sandbox/exec/trunk/src/assembly/bin.xml ( 647500 )
 /commons/sandbox/exec/trunk/src/assembly/src.xml ( 647500 )


Dependencies Changes:

No dependencies changed



Build Defintion:

POM filename: pom.xml
Goals: clean deploy   
Arguments: --batch-mode -DaltDeploymentRepository=vmbuild.repo::default::file://localhost/home/continuum/data/commons -Pci

Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: COMMONS_SCHEDULE
Profile Name: Java 5
Description: 




Test Summary:

Tests: 55
Failures: 1
Total time: 60361


Output:

[INFO] Scanning for projects...
[INFO] 

[INFO] Building Commons Exec (Sandbox)
[INFO]task-segment: [clean, deploy]
[INFO] 

[INFO] [clean:clean]
[INFO] Deleting directory /home/continuum/data/working-directory/178/target
[INFO] Deleting directory 
/home/continuum/data/working-directory/178/target/classes
[INFO] Deleting directory 
/home/continuum/data/working-directory/178/target/test-classes
[INFO] Deleting directory /home/continuum/data/working-directory/178/target/site
[INFO] [antrun:run {execution: javadoc.resources}]
[INFO] Executing tasks
[copy] Copying 2 files to 
/home/continuum/data/working-directory/178/target/apidocs/META-INF
[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 29 source files to 
/home/continuum/data/working-directory/178/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 8 source files to 
/home/continuum/data/working-directory/178/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/continuum/data/working-directory/178/target/surefire-reports

---
T E S T S
---
Running org.apache.commons.exec.environment.EnvironmentUtilTest
ANT_HOME=/opt/apache-ant-1.7.0
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
LANG=en_US.UTF-8
SUDO_COMMAND=/etc/init.d/continuum restart
PWD=/home/continuum/data/working-directory/178
SUDO_USER=wsmoak
SUDO_GID=1006
WRAPPER_BITS=32
USER=root
WRAPPER_OS=windows
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
WRAPPER_ARCH=x86
WRAPPER_PATH_SEPARATOR=:
MAVEN_TERMINATE_CMD=on
HOME=/home/wsmoak
PLEXUS_HOME=/opt/continuum-1.1-beta-3
TOOLS_JAR=/usr/lib/jvm/java-6-sun/lib/tools.jar
LESSOPEN=| /usr/bin/lesspipe %s
LD_LIBRARY_PATH=/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/client:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/jdk1.5.0_12/jre/../lib/i386:/usr/lib/jvm/jdk1.6.0_05/jre/lib/i386/client:/usr/lib/jvm/jdk1.6.0_05/jre/lib/i386:/usr/lib/jvm/jdk1.6.0_05/jre/../lib/i386
LESSCLOSE=/usr/bin/lesspipe %s %s
SSH_CONNECTION=68.3.241.21 52493 140.211.11.137 22
LOGNAME=root
SHELL=/bin/bash
SUDO_UID=1006
SSH_TTY=/dev/pts/1
SHLVL=1
WRAPPER_FILE_SEPARATOR=/
HISTCONTROL=ignoreboth
MAVEN_HOME=/opt/maven-1.0.2
M2_HOME=/opt/maven-2.0.7
SSH_CLIENT=68.3.241.21 52493 22
MAIL=/var/mail/wsmoak
JAVA_HOME=/usr/lib/jvm/jdk1.5.0_12/

[continuum] BUILD FAILURE: Commons Exec (Sandbox)

2008-04-12 Thread Continuum VMBuild Server

Online report : 
http://vmbuild.apache.org/continuum/buildResult.action?buildId=76278projectId=178

Build statistics:
 State: Failed
 Previous State: Ok
 Started at: Sat 12 Apr 2008 15:30:37 -0700
 Finished at: Sat 12 Apr 2008 15:31:56 -0700
 Total time: 1m 18s
 Build Trigger: Schedule
 Build Number: 30
 Exit code: 1
 Building machine hostname: vmbuild.apache.org
 Operating system : Linux(unknown)
 Java Home version : 
 java version 1.5.0_12

 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
 Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)
   
 Builder version :

 Maven version: 2.0.7
 Java version: 1.5.0_12
 OS name: linux version: 2.6.20-16-server arch: i386
   


SCM Changes:

Changed: niallp @ Sat 12 Apr 2008 14:51:39 -0700
Comment: Add assembly descriptors
Files changed:
 /commons/sandbox/exec/trunk/pom.xml ( 647500 )
 /commons/sandbox/exec/trunk/src/assembly ( 647500 )
 /commons/sandbox/exec/trunk/src/assembly/bin.xml ( 647500 )
 /commons/sandbox/exec/trunk/src/assembly/src.xml ( 647500 )


Dependencies Changes:

No dependencies changed



Build Defintion:

POM filename: pom.xml
Goals: clean deploy   
Arguments: --batch-mode -DaltDeploymentRepository=vmbuild.repo::default::file://localhost/home/continuum/data/commons -Pci

Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: COMMONS_SCHEDULE
Profile Name: Java 5
Description: 




Test Summary:

Tests: 55
Failures: 1
Total time: 60361


Output:

[INFO] Scanning for projects...
[INFO] 

[INFO] Building Commons Exec (Sandbox)
[INFO]task-segment: [clean, deploy]
[INFO] 

[INFO] [clean:clean]
[INFO] Deleting directory /home/continuum/data/working-directory/178/target
[INFO] Deleting directory 
/home/continuum/data/working-directory/178/target/classes
[INFO] Deleting directory 
/home/continuum/data/working-directory/178/target/test-classes
[INFO] Deleting directory /home/continuum/data/working-directory/178/target/site
[INFO] [antrun:run {execution: javadoc.resources}]
[INFO] Executing tasks
[copy] Copying 2 files to 
/home/continuum/data/working-directory/178/target/apidocs/META-INF
[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 29 source files to 
/home/continuum/data/working-directory/178/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 8 source files to 
/home/continuum/data/working-directory/178/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/continuum/data/working-directory/178/target/surefire-reports

---
T E S T S
---
Running org.apache.commons.exec.environment.EnvironmentUtilTest
ANT_HOME=/opt/apache-ant-1.7.0
XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
LANG=en_US.UTF-8
SUDO_COMMAND=/etc/init.d/continuum restart
PWD=/home/continuum/data/working-directory/178
SUDO_USER=wsmoak
SUDO_GID=1006
WRAPPER_BITS=32
USER=root
WRAPPER_OS=windows
NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
WRAPPER_ARCH=x86
WRAPPER_PATH_SEPARATOR=:
MAVEN_TERMINATE_CMD=on
HOME=/home/wsmoak
PLEXUS_HOME=/opt/continuum-1.1-beta-3
TOOLS_JAR=/usr/lib/jvm/java-6-sun/lib/tools.jar
LESSOPEN=| /usr/bin/lesspipe %s
LD_LIBRARY_PATH=/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/client:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/jdk1.5.0_12/jre/../lib/i386:/usr/lib/jvm/jdk1.6.0_05/jre/lib/i386/client:/usr/lib/jvm/jdk1.6.0_05/jre/lib/i386:/usr/lib/jvm/jdk1.6.0_05/jre/../lib/i386
LESSCLOSE=/usr/bin/lesspipe %s %s
SSH_CONNECTION=68.3.241.21 52493 140.211.11.137 22
LOGNAME=root
SHELL=/bin/bash
SUDO_UID=1006
SSH_TTY=/dev/pts/1
SHLVL=1
WRAPPER_FILE_SEPARATOR=/
HISTCONTROL=ignoreboth
MAVEN_HOME=/opt/maven-1.0.2
M2_HOME=/opt/maven-2.0.7
SSH_CLIENT=68.3.241.21 52493 22
MAIL=/var/mail/wsmoak
JAVA_HOME=/usr/lib/jvm/jdk1.5.0_12/

Re: [functor] how to eliminate test classes from m2 generated apidocs?

2008-04-12 Thread Niall Pemberton
On Wed, Apr 9, 2008 at 10:13 PM, Matt Benson [EMAIL PROTECTED] wrote:
 That pretty much sums it up.  Niall?  :)

Looks like its being caused by a bug in the taglist plugin - I've
raised an issue ticket for it here:

http://jira.codehaus.org/browse/MTAGLIST-31

Fortunately that plugin is only in commons-sandbox-parent (rather than
commons-parent). We should release commons-sandbox-parent without that
plugin to resolve this.

Niall

  -Matt

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



[VOTE] Relase Version 5 of commons-sandbox-parent

2008-04-12 Thread Niall Pemberton
Hi,

I'd like to release version 5 of the commons-sandbox-parent pom -
there are two changes since the last release:

- upgrade it to use version 9 of commons-parent
- remove the taglist-maven-plugin because of the MTAGLIST-31 bug:
   http://jira.codehaus.org/browse/MTAGLIST-31

There have been no other changes since the last release of
commons-sandbox-parent:

http://svn.apache.org/viewvc/commons/proper/commons-sandbox-parent/trunk/pom.xml?r1=647510r2=632874diff_format=h

[ ] +1
[ ] =0
[ ] -1

Vote is open for 72 hours

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



Re: [VOTE] Relase Version 5 of commons-sandbox-parent

2008-04-12 Thread Niall Pemberton
Sorry, I hadn't committed the change to commons-parent-9 - now done
and the correct URL showing the changes is

http://svn.apache.org/viewvc/commons/proper/commons-sandbox-parent/trunk/pom.xml?r1=647511r2=632874diff_format=h

Niall

On Sun, Apr 13, 2008 at 1:29 AM, Niall Pemberton
[EMAIL PROTECTED] wrote:
 Hi,

  I'd like to release version 5 of the commons-sandbox-parent pom -
  there are two changes since the last release:

  - upgrade it to use version 9 of commons-parent
  - remove the taglist-maven-plugin because of the MTAGLIST-31 bug:
http://jira.codehaus.org/browse/MTAGLIST-31

  There have been no other changes since the last release of
  commons-sandbox-parent:

  
 http://svn.apache.org/viewvc/commons/proper/commons-sandbox-parent/trunk/pom.xml?r1=647510r2=632874diff_format=h

  [ ] +1
  [ ] =0
  [ ] -1

  Vote is open for 72 hours


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



Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread Niall Pemberton
On Sat, Apr 12, 2008 at 4:50 PM, sebb [EMAIL PROTECTED] wrote:
 +1

:)

  BTW a check of SVN recommended:

  svn ps svn:eol-style native
  
 COLLECTIONS_3_2_1_RC1/src/test/org/apache/commons/collections/map/TestMultiValueMap.java

Fixed in the branch, thanks

Niall

  S///


 On 12/04/2008, Oliver Heger [EMAIL PROTECTED] wrote:
   +1
  
Artifacts look good.
  
On the site I found that the Javadoc (3.2.1 release) link in the main
menue does not work, but I assume it will when the site is deployed.
  
  
Oliver
  
  
Niall Pemberton wrote:
 The Sling project has requested an OSGi enabled release of Commons
 Collections and since it seems unlikely that Collections 3.3 will be
 ready in the timescale they require, I have created a release
 candidate for Collections 3.2.1. This is basically a re-packaging of
 the Collections 3.2 release with the appropriate OSGi meta data in the
 Collections jar. The only changes I have made to the java source code
 is to modify source file license headers to conform to current policy
 and remove tab characters. An m2 build has been added to the
 Collections 3.2 branch I created and the site has been updated to
 reflect the 3.2.1 release.

 The artifacts are here:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/

 SVN Tag:
 
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/

 Site:
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
 (note m2 generates relative links, so some don't work - but the site
 is for info and not included in the release artifacts)

 Release Notes:
 
 http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
 
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html

 RAT Report:
 
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html

 CLIRR Report:
 Clirr failed and so is not available

 RC2 has been built with m2 - but m1 and ant builds are available - 
 details here:
 
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html

 Vote is open for 72 hours

 Thanks in advance for your feedback/votes.

 Niall
 
 -

 [  ] +1  I support this release
 [  ] +0  I am OK with this release
 [  ] -0   OK, but
 [  ] -1   I do not support this release

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

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

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



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



Re: [VOTE] Release Collections 3.2.1 based on RC1

2008-04-12 Thread Niall Pemberton
On Sat, Apr 12, 2008 at 4:42 PM, Oliver Heger
[EMAIL PROTECTED] wrote:
 +1

  Artifacts look good.

  On the site I found that the Javadoc (3.2.1 release) link in the main
  menue does not work, but I assume it will when the site is deployed.

Yes, just maven screwing up with relative links, but will be OK once deployed

Niall

  Oliver

  Niall Pemberton wrote:
   The Sling project has requested an OSGi enabled release of Commons
   Collections and since it seems unlikely that Collections 3.3 will be
   ready in the timescale they require, I have created a release
   candidate for Collections 3.2.1. This is basically a re-packaging of
   the Collections 3.2 release with the appropriate OSGi meta data in the
   Collections jar. The only changes I have made to the java source code
   is to modify source file license headers to conform to current policy
   and remove tab characters. An m2 build has been added to the
   Collections 3.2 branch I created and the site has been updated to
   reflect the 3.2.1 release.
  
   The artifacts are here:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/
  
   SVN Tag:
   
 http://svn.apache.org/viewvc/commons/proper/collections/tags/COLLECTIONS_3_2_1_RC1/
  
   Site:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/site/
   (note m2 generates relative links, so some don't work - but the site
   is for info and not included in the release artifacts)
  
   Release Notes:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/RELEASE-NOTES.html
   
 http://people.apache.org/~niallp/collections-3.2.1-rc1/site/release_3_2_1.html
  
   RAT Report:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/site/rat-report.html
  
   CLIRR Report:
   Clirr failed and so is not available
  
   RC2 has been built with m2 - but m1 and ant builds are available - details 
 here:
   http://people.apache.org/~niallp/collections-3.2.1-rc1/site/building.html
  
   Vote is open for 72 hours
  
   Thanks in advance for your feedback/votes.
  
   Niall
   
 -
  
   [  ] +1  I support this release
   [  ] +0  I am OK with this release
   [  ] -0   OK, but
   [  ] -1   I do not support this release
  


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


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



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



Re: [DISCUSS] New Expressions Sandbox Project...

2008-04-12 Thread James Carman
So, does anyone have any strong opinions about the name?  I am
thinking that I should just pick one (not expression) and just go
with it.  If I change the name, I'll likely change the interface names
to match.  Anyone?

On Sat, Apr 12, 2008 at 7:22 AM, James Carman
[EMAIL PROTECTED] wrote:
 On Thu, Apr 10, 2008 at 2:29 PM, James Carman
  [EMAIL PROTECTED] wrote:
Other interesting ideas:
  
MethodPath - you're recording a path through objects via methods calls.
MethodWalker - you're walking a series of method calls.
Navigator - you're navigating through a graph of objects.
  

  Property - the settable/gettable object could just be called a Property
  PropertyRef - it could be thought of as a property reference


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