[GUMP@vmgump]: Project commons-dbcp2 (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

Project commons-dbcp2 has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 209 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-dbcp2 :  Database Connection Pool


Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-dbcp2/index.html

That said, some information snippets are provided here.

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



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-dbcp2/gump_work/build_apache-commons_commons-dbcp2.html
Work Name: build_apache-commons_commons-dbcp2 (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
dist 
[Working Directory: /srv/gump/public/workspace/apache-commons/dbcp]
CLASSPATH: 
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/apache-commons/dbcp/dist/classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/packages/jta-spec1_0_1/jta-spec1_0_1.jar:/srv/gump/packages/jdbc2_0/jdbc2_0-stdext.jar:/srv/gump/public/workspace/junit/dist/junit-27112012.jar:/srv/gump/public/workspace/junit/dist/junit-dep-27112012.jar:/srv/gump/public/workspace/apache-commons/pool/dist/commons-pool2-2.0-SNAPSHOT.jar
-
[mkdir] Created dir: 
/srv/gump/public/workspace/apache-commons/dbcp/build/classes
[javac] Compiling 52 source files to 
/srv/gump/public/workspace/apache-commons/dbcp/build/classes
[javac] 
/srv/gump/public/workspace/apache-commons/dbcp/src/java/org/apache/commons/dbcp2/BasicDataSource.java:52:
 error: BasicDataSource is not abstract and does not override abstract method 
getParentLogger() in CommonDataSource
[javac] public class BasicDataSource implements DataSource {
[javac]^
[javac] 
/srv/gump/public/workspace/apache-commons/dbcp/src/java/org/apache/commons/dbcp2/DelegatingConnection.java:65:
 error: DelegatingConnection is not abstract and does not override abstract 
method getNetworkTimeout() in Connection
[javac] public class DelegatingConnection extends AbandonedTrace
[javac]^
[javac] 
/srv/gump/public/workspace/apache-commons/dbcp/src/java/org/apache/commons/dbcp2/DelegatingStatement.java:46:
 error: DelegatingStatement is not abstract and does not override abstract 
method isCloseOnCompletion() in Statement
[javac] public class DelegatingStatement extends AbandonedTrace implements 
Statement {
[javac]^
[javac] 
/srv/gump/public/workspace/apache-commons/dbcp/src/java/org/apache/commons/dbcp2/DelegatingPreparedStatement.java:57:
 error: DelegatingPreparedStatement is not abstract and does not override 
abstract method isCloseOnCompletion() in Statement
[javac] public class DelegatingPreparedStatement extends DelegatingStatement
[javac]^
[javac] 
/srv/gump/public/workspace/apache-commons/dbcp/src/java/org/apache/commons/dbcp2/DelegatingCallableStatement.java:58:
 error: DelegatingCallableStatement is not abstract and does not override 
abstract method getObject(String,Class) in CallableStatement
[javac] public class DelegatingCallableStatement extends 
DelegatingPreparedStatement
[javac]^
[javac]   where T is a type-variable:
[javac] T extends Object declared in method 
getObject(String,Class)
[javac] 
/srv/gump/public/workspace/apache-commons/dbcp/src/java/org/apache/commons/dbcp2/DelegatingDatabaseMetaData.java:36:
 error: DelegatingDatabaseMetaData is not abstract and does not override 
abstract method generatedKeyAlwaysReturned() in DatabaseMetaData
[javac] public clas

[GUMP@vmgump]: Project commons-dbcp (in module commons-dbcp-1.x) failed

[Gump]

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 gene...@gump.apache.org.

Project commons-dbcp has an issue affecting its community integration.
This issue affects 18 projects,
 and has been outstanding for 40 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-dbcp :  Object Pooling
- db-ddlutils :  Easy-to-use component for working with Database Definition 
(...
- jakarta-tomcat-4.0 :  Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-dbcp :  Servlet 2.4 and JSP 2.0 Reference Implementation
- jakarta-tomcat-jk :  Connectors to various web servers
- javax.el :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation (for 
...
- javax.servlet :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation 
(for ...
- javax.servlet.jsp :  Java Servlet 2.5 & Server Pages JSP 2.1 
implementation (for ...
- solr :  Java Based Search Engine
- solr-test :  Java Based Search Engine
- tomcat-tc6 :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation (for 
...
- tomcat-tc7.0.x :  Tomcat 7.x, a web server implementing Java Servlet 3.0,
...
- tomcat-tc7.0.x-dbcp :  Tomcat 7.x, a web server implementing Java Servlet 
3.0,
...
- tomcat-tc7.0.x-test :  Tomcat 7.x, a web server implementing Java Servlet 
3.0,
...
- tomcat-trunk :  Tomcat 8.x, a web server implementing Java Servlet 3.1,
...
- tomcat-trunk-dbcp :  Tomcat 8.x, a web server implementing Java Servlet 
3.1,
...
- tomcat-trunk-test :  Tomcat 8.x, a web server implementing Java Servlet 
3.1,
...


Full details are available at:

http://vmgump.apache.org/gump/public/commons-dbcp-1.x/commons-dbcp/index.html

That said, some information snippets are provided here.

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



The following work was performed:
http://vmgump.apache.org/gump/public/commons-dbcp-1.x/commons-dbcp/gump_work/build_commons-dbcp-1.x_commons-dbcp.html
Work Name: build_commons-dbcp-1.x_commons-dbcp (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
dist 
[Working Directory: /srv/gump/public/workspace/commons-dbcp-1.x]
CLASSPATH: 
/usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/junit/dist/junit-27112012.jar:/srv/gump/public/workspace/junit/dist/junit-dep-27112012.jar:/srv/gump/packages/jta-spec1_0_1/jta-spec1_0_1.jar:/srv/gump/public/workspace/commons-pool-1.x/dist/commons-pool-1.6.1-SNAPSHOT.jar
-
[javac]^
[javac]   where T is a type-variable:
[javac] T extends Object declared in method 
getObject(String,Class)
[javac] 
/srv/gump/public/workspace/commons-dbcp-1.x/src/java/org/apache/commons/dbcp/DelegatingConnection.java:65:
 error: DelegatingConnection is not abstract and does not override abstract 
method getNetworkTimeout() in Connection
[javac] public class DelegatingConnection extends AbandonedTrace
[javac]^
[javac] 
/srv/gump/public/workspace/commons-dbcp-1.x/src/java/org/apache/commons/dbcp/DelegatingDatabaseMetaData.java:38:
 error: DelegatingDatabaseMetaData is not abstract and does not override 
abstract method generatedKeyAlwaysReturned() in DatabaseMetaData
[javac] public class DelegatingDatabaseMetaData extends AbandonedTrace
[javac]^
[javac] 
/srv/gump/public/workspace/commons-dbcp-1.x/src/java/org/apache/commons/dbcp/DelegatingResultSet.java:61:
 error: DelegatingResultSet is not abstract and does not override abstract 
method getObject(String,Class) in ResultSet
[javac] public class DelegatingResultSet extends Aban

Re: [math] Second thoughts on MATH-803 and "zip-visitor" for vectors.

[Sébastien Brisard]

Hi,


2012/11/27 Gilles Sadowski 

> Hello.
>
> > > > in MATH-803 [1] it was decided to deprecate
> > > RealVector.ebeMultiply/Divide,
> > > > because these methods were difficult to support with sparse vectors.
> > > > However, in MATH-870, we decided to deprecate sparse vectors
> altogether.
> > > >
> > > > I'm therefore having second thoughts on MATH-803. Since the
> problematic
> > > > implementations of RealVector are removed, why not keep these quite
> handy
> > > > methods?
>
> The goal was also to "clean up" the matrix and vector implementations.
>
> True, but all good scientific packages (matlab, scilab, numpy) have these
operations. If we do not keep them in the interface of RealVector (which
I'm OK about), we need to provide a clean alternative. At the moment,
visitors are not clean.


> I'd rather suggest to add such features in the "MathArrays" class:
> -
> public static double[] ebeDivide(double[] numer,
>  double[] denom) {
>   if (numer.length != denom.length) {
> throw new DimensionMismatchException(numer.length, denom.length);
>   }
>
>   final double[] result = numer.clone();
>   for (int i = 0; i < numer.length; i++) {
> result[i] /= denom[i];
>   }
>
>   return result;
> }
> -
>

I'm not adverse to the idea, but actually, cleaning recently took place the
other way round. In RealVector, we removed all methods which took an array
in place of a vector, since constructing an ArrayRealVector from an array
is almost costless (using the right constructor).


>
> What do you think?
>
> Gilles
>
> > [...]
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
> Best regards,
Sébastien

Re: [math] Checking preconditions on package private functions

[Sébastien Brisard]

Hi,


2012/11/26 Gilles Sadowski 

> Hi.
>
> > in classes Gamma and Beta, some functions are package private:
> >   - logGammaSum
> >   - logGammaMinusLogGammaSum (for lack of a better name)
> >   - bcorr
> > These functions are meant to be used by other functions,
>
> None of these functions seem to used. Am I missing something?
>
> None of these functions are used YET, they are going to be used in the new
implementation of logBeta. I wouldn't have committed tortuous, useless,
package private functions just for the sake of cluttering the code!

S.

Gilles
>
> > like logBeta. Each
> > of these functions have their own domain, and in logBeta, we make sure
> not
> > to call them outside this domain.
> > For the time being, I've implemented explicit checks on the arguments +
> > exceptions in these auxiliary functions. I guess this comes with a cost,
> > which is arguably unnecessary.
> > Should I remove these tests, and clearly state in the Javadoc that the
> > caller should make sure that the argument is valid?
> > I'm OK with both solutions (keeping/removing the tests).
> >
> > Best regards,
> > Sébastien
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [math] Second thoughts on MATH-803 and "zip-visitor" for vectors.

[Gilles Sadowski]

Hello.

> > > in MATH-803 [1] it was decided to deprecate
> > RealVector.ebeMultiply/Divide,
> > > because these methods were difficult to support with sparse vectors.
> > > However, in MATH-870, we decided to deprecate sparse vectors altogether.
> > >
> > > I'm therefore having second thoughts on MATH-803. Since the problematic
> > > implementations of RealVector are removed, why not keep these quite handy
> > > methods?

The goal was also to "clean up" the matrix and vector implementations.

I'd rather suggest to add such features in the "MathArrays" class:
-
public static double[] ebeDivide(double[] numer,
 double[] denom) {
  if (numer.length != denom.length) {
throw new DimensionMismatchException(numer.length, denom.length);
  }

  final double[] result = numer.clone();
  for (int i = 0; i < numer.length; i++) {
result[i] /= denom[i];
  }

  return result;
}
-

What do you think?

Gilles

> [...]

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [math] Checking preconditions on package private functions

[Gilles Sadowski]

Hi.

> in classes Gamma and Beta, some functions are package private:
>   - logGammaSum
>   - logGammaMinusLogGammaSum (for lack of a better name)
>   - bcorr
> These functions are meant to be used by other functions, 

None of these functions seem to used. Am I missing something?

Gilles

> like logBeta. Each
> of these functions have their own domain, and in logBeta, we make sure not
> to call them outside this domain.
> For the time being, I've implemented explicit checks on the arguments +
> exceptions in these auxiliary functions. I guess this comes with a cost,
> which is arguably unnecessary.
> Should I remove these tests, and clearly state in the Javadoc that the
> caller should make sure that the argument is valid?
> I'm OK with both solutions (keeping/removing the tests).
> 
> Best regards,
> Sébastien

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[math] Checking preconditions on package private functions

[Sébastien Brisard]

Hi,
in classes Gamma and Beta, some functions are package private:
  - logGammaSum
  - logGammaMinusLogGammaSum (for lack of a better name)
  - bcorr
These functions are meant to be used by other functions, like logBeta. Each
of these functions have their own domain, and in logBeta, we make sure not
to call them outside this domain.
For the time being, I've implemented explicit checks on the arguments +
exceptions in these auxiliary functions. I guess this comes with a cost,
which is arguably unnecessary.
Should I remove these tests, and clearly state in the Javadoc that the
caller should make sure that the argument is valid?
I'm OK with both solutions (keeping/removing the tests).

Best regards,
Sébastien

Re: [VOTE] Release NET 3.2 based on RC1

[sebb]

On 26 November 2012 19:08, Gary Gregory  wrote:
> Hi,
>
> I thought we had a policy to keep BC for minor releases?

Yes.

> I understand that the removed methods are not in core classes but it still
> breaks BC. Are sure we want that? Are the removed methods confusing in a
> way that can be construed as keeping them being a bug?

If the code is not being used by external clients then BC
compatibility is irrelevant.
This is the case here.

> Gary
>
> On Mon, Nov 26, 2012 at 1:29 PM, sebb  wrote:
>
>> This is a vote to release Apache Commons NET 3.2 based on RC1.
>>
>> [ ] +1 release it
>> [ ] +0 go ahead I don't care
>> [ ] -1 no, do not release it because...
>>
>> tag:
>> https://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_2_RC1/(r1413727)
>>
>> site:
>> http://people.apache.org/~sebb/net-3.2-RC1/
>>
>> The Javadocs (1.4.1) link does not work, nor does the download link.
>> These will be OK once the site is deployed.
>>
>> Source and binary archives (tar.gz and .zip) and Maven jars:
>> https://repository.apache.org/content/repositories/orgapachecommons-078/
>>
>> [The tar.gz and .zip files will be moved to dist/commons/net before
>> promoting the Maven jars to release status]
>>
>> Vote will remain open for at least 72 hours.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release NET 3.2 based on RC1

[Gary Gregory]

Hi,

I thought we had a policy to keep BC for minor releases?

I understand that the removed methods are not in core classes but it still
breaks BC. Are sure we want that? Are the removed methods confusing in a
way that can be construed as keeping them being a bug?

Gary

On Mon, Nov 26, 2012 at 1:29 PM, sebb  wrote:

> This is a vote to release Apache Commons NET 3.2 based on RC1.
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because...
>
> tag:
> https://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_2_RC1/(r1413727)
>
> site:
> http://people.apache.org/~sebb/net-3.2-RC1/
>
> The Javadocs (1.4.1) link does not work, nor does the download link.
> These will be OK once the site is deployed.
>
> Source and binary archives (tar.gz and .zip) and Maven jars:
> https://repository.apache.org/content/repositories/orgapachecommons-078/
>
> [The tar.gz and .zip files will be moved to dist/commons/net before
> promoting the Maven jars to release status]
>
> Vote will remain open for at least 72 hours.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[VOTE] Release NET 3.2 based on RC1

[sebb]

This is a vote to release Apache Commons NET 3.2 based on RC1.

[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because...

tag:
https://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_2_RC1/ (r1413727)

site:
http://people.apache.org/~sebb/net-3.2-RC1/

The Javadocs (1.4.1) link does not work, nor does the download link.
These will be OK once the site is deployed.

Source and binary archives (tar.gz and .zip) and Maven jars:
https://repository.apache.org/content/repositories/orgapachecommons-078/

[The tar.gz and .zip files will be moved to dist/commons/net before
promoting the Maven jars to release status]

Vote will remain open for at least 72 hours.

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Moving to svnpubsub for dist releases

[Ralph Goers]

Traceability by who?

PMC members can easily verify that what is committed to dist matches what they 
verified using what they downloaded and the MD5s that came with them.  They are 
the ones responsible for the vote and the artifacts so I don't see a problem 
with that.  Why you would need some sort of formal linking once the artifacts 
are published escapes me.

Ralph


On Nov 26, 2012, at 9:23 AM, sebb wrote:

> On 26 November 2012 17:01, Ralph Goers  wrote:
>> Actually, if you use the Release plugin the artifacts will be uploaded to 
>> the staging repository. At least that is what VFS does.  They can be voted 
>> on there and then checked into SVN.  You can easily verify they didn't 
>> change because the MD5s go along with them.
> 
> But do the MD5s get automatically added to the release vote?
> And how can one prove later that the MD5s in the VOTE thread are the
> same as the ones in the staging repo?
> 
> AFAICT that is no different from uploading to anywhere else, unless I
> misunderstand what the release staging repository is.
> 
> The point is that uploading to SVN and voting on the URL+revision
> automatically provides traceability.
> Whereas AFAICT the other methods don't, at least not without
> additional work by the RM and all reviewers.
> 
>> Ralph
>> 
>> On Nov 26, 2012, at 8:41 AM, sebb wrote:
>> 
>>> On 26 November 2012 11:24, sebb  wrote:
 On 26 November 2012 09:53, Emmanuel Bourg  wrote:
> Le 26/11/2012 01:01, sebb a écrit :
> 
>> Hope this all makes sense!
> 
> Well, maybe I misunderstood, but committing the RC sites for review into
> a SVN repository seems a bit convoluted to me. A good old upload on
> people.apache.org was perfectly fine.
 
 AIUI that's what infra want.
>>> 
>>> If the dist/dev URL (plus revision) is used in the vote thread, it's
>>> possible to easily trace the files from the ASF mirror back to the
>>> actual files used in the vote.
>>> 
>>> This is not nearly so easy if the files are just uploaded to a user
>>> directory on minotaur - there's no proof that the the files that were
>>> voted on are the ones that were eventually released.
>>> 
>>> At some point the files must be uploaded to SVN; once in SVN they can
>>> be moved around very cheaply.
>>> 
> Emmanuel Bourg
> 
> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Moving to svnpubsub for dist releases

[Mark Thomas]

On 26/11/2012 17:23, sebb wrote:
> On 26 November 2012 17:01, Ralph Goers  wrote:
>> Actually, if you use the Release plugin the artifacts will be uploaded to 
>> the staging repository. At least that is what VFS does.  They can be voted 
>> on there and then checked into SVN.  You can easily verify they didn't 
>> change because the MD5s go along with them.
> 
> But do the MD5s get automatically added to the release vote?
> And how can one prove later that the MD5s in the VOTE thread are the
> same as the ones in the staging repo?
> 
> AFAICT that is no different from uploading to anywhere else, unless I
> misunderstand what the release staging repository is.
> 
> The point is that uploading to SVN and voting on the URL+revision
> automatically provides traceability.
> Whereas AFAICT the other methods don't, at least not without
> additional work by the RM and all reviewers.

That may be the case (I haven't thought through the logic) but it is not
the primary driver.

The primary driver is removing the need to hand out a shell account on
people.a.o to every committer.

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [CSV] Discussion about the new CSVFormatBuilder

[Gary Gregory]

Now what?

I'd like to release a 1.0 but we need to come to some agreement on a config
API...

Gary

On Thu, Nov 22, 2012 at 3:16 AM, Benedikt Ritter wrote:

> Maybe we first have to decide if we want validation of CSVFormats at
> construction time or not. If not, the changes of CSV-68 can be reverted.
>
> Benedikt
>
> 2012/11/21 James Carman 
>
> > I don't really have a problem with the extra call to build() before
> > you have something useful.  It does give us the ability to do
> > validation on the object before you build it.  If we choose not to do
> > the validation at this time, that's fine, but if we ever do choose to
> > add that in the future, we don't have to break API backward
> > compatibility to do so.
> >
> > On Tue, Nov 20, 2012 at 5:57 PM, Gary Gregory 
> > wrote:
> > > Ok this is good. Let's see some healthy debating. :)
> > >
> > > What is the alternate API?
> > >
> > > To me the bother is the extra build() call, but that's the pattern.
> > >
> > > Could an alt API be used and co-exist?
> > >
> > > Is making the ctor an option? It would have to do some validation.
> > >
> > > Gary
> > >
> > > On Nov 20, 2012, at 16:59, Emmanuel Bourg  wrote:
> > >
> > >> Le 20/11/2012 20:01, Benedikt Ritter a écrit :
> > >>
> > >>> Please share your thoughts about the builder.
> > >>
> > >> Sorry Benedikt but I have to say I really don't like this design. I
> > >> prefer a simpler API for the reasons you mentioned in the
> disadvantages.
> > >> The minor improvements from the developer's point of view are much
> less
> > >> important than the ease of use from user's point of view.
> > >>
> > >> Emmanuel Bourg
> > >>
> > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Moving to svnpubsub for dist releases

[sebb]

On 26 November 2012 17:01, Ralph Goers  wrote:
> Actually, if you use the Release plugin the artifacts will be uploaded to the 
> staging repository. At least that is what VFS does.  They can be voted on 
> there and then checked into SVN.  You can easily verify they didn't change 
> because the MD5s go along with them.

But do the MD5s get automatically added to the release vote?
And how can one prove later that the MD5s in the VOTE thread are the
same as the ones in the staging repo?

AFAICT that is no different from uploading to anywhere else, unless I
misunderstand what the release staging repository is.

The point is that uploading to SVN and voting on the URL+revision
automatically provides traceability.
Whereas AFAICT the other methods don't, at least not without
additional work by the RM and all reviewers.

> Ralph
>
> On Nov 26, 2012, at 8:41 AM, sebb wrote:
>
>> On 26 November 2012 11:24, sebb  wrote:
>>> On 26 November 2012 09:53, Emmanuel Bourg  wrote:
 Le 26/11/2012 01:01, sebb a écrit :

> Hope this all makes sense!

 Well, maybe I misunderstood, but committing the RC sites for review into
 a SVN repository seems a bit convoluted to me. A good old upload on
 people.apache.org was perfectly fine.
>>>
>>> AIUI that's what infra want.
>>
>> If the dist/dev URL (plus revision) is used in the vote thread, it's
>> possible to easily trace the files from the ASF mirror back to the
>> actual files used in the vote.
>>
>> This is not nearly so easy if the files are just uploaded to a user
>> directory on minotaur - there's no proof that the the files that were
>> voted on are the ones that were eventually released.
>>
>> At some point the files must be uploaded to SVN; once in SVN they can
>> be moved around very cheaply.
>>
 Emmanuel Bourg


>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Moving to svnpubsub for dist releases

[Ralph Goers]

Actually, if you use the Release plugin the artifacts will be uploaded to the 
staging repository. At least that is what VFS does.  They can be voted on there 
and then checked into SVN.  You can easily verify they didn't change because 
the MD5s go along with them.

Ralph

On Nov 26, 2012, at 8:41 AM, sebb wrote:

> On 26 November 2012 11:24, sebb  wrote:
>> On 26 November 2012 09:53, Emmanuel Bourg  wrote:
>>> Le 26/11/2012 01:01, sebb a écrit :
>>> 
 Hope this all makes sense!
>>> 
>>> Well, maybe I misunderstood, but committing the RC sites for review into
>>> a SVN repository seems a bit convoluted to me. A good old upload on
>>> people.apache.org was perfectly fine.
>> 
>> AIUI that's what infra want.
> 
> If the dist/dev URL (plus revision) is used in the vote thread, it's
> possible to easily trace the files from the ASF mirror back to the
> actual files used in the vote.
> 
> This is not nearly so easy if the files are just uploaded to a user
> directory on minotaur - there's no proof that the the files that were
> voted on are the ones that were eventually released.
> 
> At some point the files must be uploaded to SVN; once in SVN they can
> be moved around very cheaply.
> 
>>> Emmanuel Bourg
>>> 
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Moving to svnpubsub for dist releases

[sebb]

On 26 November 2012 11:24, sebb  wrote:
> On 26 November 2012 09:53, Emmanuel Bourg  wrote:
>> Le 26/11/2012 01:01, sebb a écrit :
>>
>>> Hope this all makes sense!
>>
>> Well, maybe I misunderstood, but committing the RC sites for review into
>> a SVN repository seems a bit convoluted to me. A good old upload on
>> people.apache.org was perfectly fine.
>
> AIUI that's what infra want.

If the dist/dev URL (plus revision) is used in the vote thread, it's
possible to easily trace the files from the ASF mirror back to the
actual files used in the vote.

This is not nearly so easy if the files are just uploaded to a user
directory on minotaur - there's no proof that the the files that were
voted on are the ones that were eventually released.

At some point the files must be uploaded to SVN; once in SVN they can
be moved around very cheaply.

>> Emmanuel Bourg
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons Daemon 1.0.11

[Gary Gregory]

+1 then (tested X86 native build on Windows 7 with MS VS 2010)

Gary

On Sun, Nov 25, 2012 at 5:32 PM, Mladen Turk  wrote:

> On 11/25/2012 09:42 PM, Gary Gregory wrote:
>
>> Is this something to worry about:
>>
>>
> Nope.
>
>
>  .\..\..\apps\prunsrv\prunsrv.**c(317) : warning C4996: '_wfopen': This
>> function or variable may be unsafe. Consider using _wfopen_s instead. To
>> disable deprecatio
>> n, use _CRT_SECURE_NO_WARNINGS. See online help for details.
>>
>
> If it bothers you you can
> C:\> set "EXTRA_CFLAGS=-D_CRT_SECURE_**NO_WARNINGS"
> C:\> nmake
>
> It will just shut up the compiler.
>
>
>
> Regards
> --
> ^TM
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@commons.**apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

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


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/scxml/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html
Work Name: build_apache-commons_commons-scxml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 24 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -Dsimplelog.defaultlog=info 
--settings 
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/scxml]
M2_HOME: /opt/maven2
-
[INFO] SimpleSCXMLListener - /s2/s2.1/e1.2
[INFO] SimpleSCXMLListener - /s2/s2.1/e1.2
[INFO] SimpleSCXMLListener - /s2/s2.1
[INFO] SimpleSCXMLListener - /s2
[INFO] SimpleSCXMLListener - transition (event = s2.1.done, cond = null, from = 
/s2, to = /s3)
[INFO] SimpleSCXMLListener - /s3
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.289 sec
Running org.apache.commons.scxml.issues.Issue64Test
[INFO] SCXMLSemantics - null: Begin transition bug test ...
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SCXMLSemantics - null: somedata
[INFO] SCXMLSemantics - null: *somedata
[INFO] SimpleSCXMLListener - transition (event = show.bug, cond = null, from = 
/tranbug, to = /end)
[INFO] SimpleSCXMLListener - /end
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:30:21
 and digester match "scxml/datamodel/misplaced"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:36:19
 and digester match "scxml/state/onentry/foo"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://my.foo.example/"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:37:22
 and digester match "scxml/state/onentry/bar"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:41:21
 and digester match "scxml/state/transition/datamodel"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:42:41
 and digester match "scxml/state/transition/datamodel/data"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://my.foo.example/"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:49:14
 and digester match "scxml/baz"
[INFO] SCXMLSemantics - null: Begin transition bug test ...
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SCXMLSemantics - null: null
[WARN] SimpleErrorReporter - EXPRESSION_ERROR (eval(''*' + dummy'):null): 
[INFO] SimpleSCXMLListener - transition (event = show.bug, cond = null, from = 
/tranbug, to = /end)
[INFO] SimpleSCXMLListener - /end
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.074 sec

Results :

Failed tests: 
  testCustomActionCallbacks(org.apache.commons.scxml.model.CustomActionTest)

Tests run: 229, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO

Re: [math] Second thoughts on MATH-803 and "zip-visitor" for vectors.

[Sébastien Brisard]

Hi,


2012/11/26 Gilles Sadowski 

> On Sun, Nov 25, 2012 at 06:00:06PM +0100, Sébastien Brisard wrote:
> > Hi,
> > in MATH-803 [1] it was decided to deprecate
> RealVector.ebeMultiply/Divide,
> > because these methods were difficult to support with sparse vectors.
> > However, in MATH-870, we decided to deprecate sparse vectors altogether.
> >
> > I'm therefore having second thoughts on MATH-803. Since the problematic
> > implementations of RealVector are removed, why not keep these quite handy
> > methods?
> >
> > BTW, these methods could be implemented with visitors, but the current
> > interface of vector visitors allows visiting only ONE vector at a time.
> So
> > visiting TWO vectors simultaneously requires uggly tweaking of this
> > interface (basically, storing a reference of one of the two vectors to be
> > visited as a class variable of the visitor itself... so much for
> > imutability).
> >
> > How about we introduce "zip-visitors" to visit simultaneously two
> vectors?
>
> I don't know the phrase "zip-visitors".
>
>
> It's probably not the best name for such a visitor. Python has a zip()
function [1] which takes a number of lists and return a single list of
tuples. You can then apply functional programming concepts to the newly
created list.

>
> How would they work?
>
That's for us to figure out. We could have something like "walk(vector1,
vector2, visitor)", where the visitor would take three arguments : an int
(the index), and two doubles (the left and right value).
Note that if we go for this, we should really think about doing the same
with the RealVector.map(), as element-by-element multiplication/division is
has more to do with mapping a bivariate function, rather than visiting two
vectors). The reason I'm implementing it at the moment with a visitor is
because I need to store locally (in the visitor) one of the two vectors,
and I need to know whic component of this local copy I need to combine to
the component of the vector on which 'visitXXX' is called. Not sure I'm
very clear.

Again, there is no time constraint on this, I just thought we could start
thinking about it.

Sébastien

[1] http://docs.python.org/2/library/functions.html#zip

> Regards,
> Gilles
>
> > This is just an idea, it can of course wait until 3.2, but if we agree
> upon
> > the idea, I can file a JIRA ticket for the record.
> >
> > Best regards,
> >
> > Sébastien
> >
> > [1] https://issues.apache.org/jira/browse/MATH-803
> > [2] https://issues.apache.org/jira/browse/MATH-870
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons Daemon 1.0.11

[Jess Holle]

My vote doesn't count, but for what it's worth, 1.0.11 seems to be 
working fine -- and to allow the Windows service mechanism to perform 
automatic restart upon failure (on request).


On 11/22/2012 7:22 AM, Mladen Turk wrote:

Apache Commons Daemon 1.0.11 based on RC1 is ready.
Binaries and sources for testing are at [1], site can be
found at [2]. Tag is [3] which will be renamed to 
COMMONS_DAEMON_1_0_11 if voted.


Please vote (vote will remain open for at least 72 hours).

Apache Commons Daemon 1.0.11 is
  [ X ] +1 Release
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...


[1] http://people.apache.org/~mturk/daemon-1.0.11/
[2] http://people.apache.org/~mturk/daemon-1.0.11-site/
[3] 
https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_11_RC1/



Regards



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [math] Second thoughts on MATH-803 and "zip-visitor" for vectors.

[Gilles Sadowski]

On Sun, Nov 25, 2012 at 06:00:06PM +0100, Sébastien Brisard wrote:
> Hi,
> in MATH-803 [1] it was decided to deprecate RealVector.ebeMultiply/Divide,
> because these methods were difficult to support with sparse vectors.
> However, in MATH-870, we decided to deprecate sparse vectors altogether.
> 
> I'm therefore having second thoughts on MATH-803. Since the problematic
> implementations of RealVector are removed, why not keep these quite handy
> methods?
> 
> BTW, these methods could be implemented with visitors, but the current
> interface of vector visitors allows visiting only ONE vector at a time. So
> visiting TWO vectors simultaneously requires uggly tweaking of this
> interface (basically, storing a reference of one of the two vectors to be
> visited as a class variable of the visitor itself... so much for
> imutability).
> 
> How about we introduce "zip-visitors" to visit simultaneously two vectors?

I don't know the phrase "zip-visitors".
How would they work?

Regards,
Gilles

> This is just an idea, it can of course wait until 3.2, but if we agree upon
> the idea, I can file a JIRA ticket for the record.
> 
> Best regards,
> 
> Sébastien
> 
> [1] https://issues.apache.org/jira/browse/MATH-803
> [2] https://issues.apache.org/jira/browse/MATH-870

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-dbutils (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

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


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [commons-dbutils-*[0-9T].jar] identifier set to 
project name
 -INFO- Optional dependency mockito failed with reason build failed
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/dbutils/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/dbutils/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/dbutils/target/surefire-reports
 -WARNING- No directory 
[/srv/gump/public/workspace/apache-commons/dbutils/target/surefire-reports]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-dbutils/gump_work/build_apache-commons_commons-dbutils.html
Work Name: build_apache-commons_commons-dbutils (Type: Build)
Work ended in a state of : Failed
Elapsed: 16 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/dbutils/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/dbutils]
M2_HOME: /opt/maven2
-
1K downloaded  (mockito-core-1.9.0.pom)
Downloading: 
http://localhost:8192/maven2/org/hamcrest/hamcrest-all/1.1/hamcrest-all-1.1.pom
479b downloaded  (hamcrest-all-1.1.pom)
Downloading: 
http://localhost:8192/maven2/org/mockito/mockito-core/1.9.0/mockito-core-1.9.0.jar
Downloading: 
http://localhost:8192/maven2/org/hamcrest/hamcrest-all/1.1/hamcrest-all-1.1.jar
273K downloaded  (hamcrest-all-1.1.jar)
1381K downloaded  (mockito-core-1.9.0.jar)
[INFO] [antrun:run {execution: javadoc.resources}]
[INFO] Executing tasks

main:
 [copy] Copying 2 files to 
/srv/gump/public/workspace/apache-commons/dbutils/target/apidocs/META-INF
[INFO] Executed tasks
[WARNING] The parameter expression: 'project.build.resources' used in mojo: 
'process' has been deprecated. Use 'project.resources' instead.
[INFO] [remote-resources:process {execution: default}]
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd 
/srv/gump/public/workspace/apache-commons/dbutils && svn --non-interactive info
[INFO] Working directory: /srv/gump/public/workspace/apache-commons/dbutils
[INFO] Storing buildNumber: ?? at timestamp: 1353931300986
[INFO] Executing: /bin/sh -c cd 
/srv/gump/public/workspace/apache-commons/dbutils && svn --non-interactive info
[INFO] Working directory: /srv/gump/public/workspace/apache-commons/dbutils
[INFO] Storing buildScmBranch: UNKNOWN_BRANCH
[debug] execute contextualize
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/srv/gump/public/workspace/apache-commons/dbutils/src/main/resources
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 29 source files to 
/srv/gump/public/workspace/apache-commons/dbutils/target/classes
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/srv/gump/public/workspace/apache-commons/dbutils/src/main/java/org/apache/commons/dbutils/DbUtils.java:[334,25]
 error: DriverProxy is not abstract and does not override abstract method 
getParentLogger() in Driver
[INFO] 1 error
[INFO] -
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure
/srv/gump/public/workspace/apache-commons/dbutils/src/main/java/org/apache/commons/dbutils/DbUtils.java:[334,25]
 error: DriverProxy is not abstract and does not override abstract method 
getParentLogger() in Driver

[INFO] 
[INFO] For more information, run Mav

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

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


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html
Work Name: build_apache-commons_commons-proxy-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/proxy]
M2_HOME: /opt/maven2
-
Running org.apache.commons.proxy.factory.util.TestMethodSignature
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec

Results :

Tests in error: 
  
testMethodInvocationImplementation(org.apache.commons.proxy.interceptor.TestMethodInterceptorAdapter)
  
testMethodInterception(org.apache.commons.proxy.interceptor.TestMethodInterceptorAdapter)
  
testSerialization(org.apache.commons.proxy.interceptor.TestMethodInterceptorAdapter)
  testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker)
  
testMethodInvocation(org.apache.commons.proxy.invoker.TestInvocationHandlerAdapter)
  
testInterceptorEquals(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInvokerEquals(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInvokerWithSuperclass(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testProxiesWithClashingFinalMethodInSuperclass(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInterceptorWithSuperclass(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInvokerHashCode(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testBooleanInterceptorParameter(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testChangingArguments(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testCreateInterceptorProxy(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInterceptingProxyClassCaching(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInterceptingProxySerializable(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInterceptorProxyWithCheckedException(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInterceptorProxyWithUncheckedException(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInvokerProxy(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInvokerProxyClassCaching(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInvokerProxySerializable(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testMethodInvocationClassCaching(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testMethodInvocationDuplicateMethods(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testMethodInvocationImplementation(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testInterceptorHashCode(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  
testWithNonAccessibleTargetType(org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory)
  testCreateNullObject(org.apache.commons.proxy.TestProxyUtils)
  testCreateNullObjectWithClassLoader(org.apache.commons.proxy.TestProxyUtils)

Tests run: 179, Failures: 0, Errors: 28, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There 

Re: Moving to svnpubsub for dist releases

[sebb]

On 26 November 2012 09:53, Emmanuel Bourg  wrote:
> Le 26/11/2012 01:01, sebb a écrit :
>
>> Hope this all makes sense!
>
> Well, maybe I misunderstood, but committing the RC sites for review into
> a SVN repository seems a bit convoluted to me. A good old upload on
> people.apache.org was perfectly fine.

AIUI that's what infra want.

> Emmanuel Bourg
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-chain2 (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

Project commons-chain2 has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 229 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-chain2 :  GoF "Chain of Responsibility" pattern


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [commons-chain2-*[0-9T].jar] identifier set to project 
name
 -DEBUG- Sole pom output [pom.xml] identifier set to project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/chain/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/chain/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-chain2/gump_work/build_apache-commons_commons-chain2.html
Work Name: build_apache-commons_commons-chain2 (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 19 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/chain/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/chain]
M2_HOME: /opt/maven2
-
[INFO] Building war: 
/srv/gump/public/workspace/apache-commons/chain/apps/cookbook-examples/target/chain-cookbook-examples-2.0-SNAPSHOT.war
[INFO] 
[INFO] Building Apache Commons Chain :: Distribution Packages
[INFO]task-segment: [package]
[INFO] 
[INFO] snapshot org.apache.commons:commons-chain2-configuration:2.0-SNAPSHOT: 
checking for updates from apache.snapshots
Downloading: 
http://localhost:8192/repo/m2-snapshot-repository/org/apache/commons/commons-chain2-configuration/2.0-SNAPSHOT/commons-chain2-configuration-2.0-SNAPSHOT.pom
[INFO] Unable to find resource 
'org.apache.commons:commons-chain2-configuration:pom:2.0-SNAPSHOT' in 
repository apache.snapshots (http://repository.apache.org/snapshots)
Downloading: 
http://localhost:8192/repo/m2-snapshot-repository/org/apache/commons/commons-chain2-configuration/2.0-SNAPSHOT/commons-chain2-configuration-2.0-SNAPSHOT.jar
[INFO] Unable to find resource 
'org.apache.commons:commons-chain2-configuration:jar:2.0-SNAPSHOT' in 
repository apache.snapshots (http://repository.apache.org/snapshots)
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.commons:commons-chain2-configuration:jar:2.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.commons 
-DartifactId=commons-chain2-configuration -Dversion=2.0-SNAPSHOT 
-Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.commons 
-DartifactId=commons-chain2-configuration -Dversion=2.0-SNAPSHOT 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.commons:commons-chain2:pom:2.0-SNAPSHOT
2) org.apache.commons:commons-chain2-configuration:jar:2.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.commons:commons-chain2:pom:2.0-SNAPSHOT

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2),
  gump-apache.snapshots (http://localhost:8192/repo/m2-snapshot-repository)



[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 minute 17 seconds
[INFO] Finished at: Mon Nov 26 11:21:07 UTC 2012
[INFO] Final Memory: 114M/241M
[INFO] 
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apache-commons/commons-chain2/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/apache-commons/comm

[GUMP@vmgump]: Project commons-digester3 (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

Project commons-digester3 has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 38 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-digester3 :  XML to Java Object Configuration
- commons-digester3-test :  Apache Commons


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [commons-digester3-*[0-9T].jar] identifier set to 
project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/apache-commons/digester/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 7 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml 
package 
[Working Directory: /srv/gump/public/workspace/apache-commons/digester]
M2_HOME: /opt/maven2
-
[INFO] [remote-resources:process {execution: default}]
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor && svn 
--non-interactive info
[INFO] Working directory: 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor
[INFO] Storing buildNumber: ?? at timestamp: 1353924260014
[INFO] Executing: /bin/sh -c cd 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor && svn 
--non-interactive info
[INFO] Working directory: 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor
[INFO] Storing buildScmBranch: UNKNOWN_BRANCH
[debug] execute contextualize
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 5 source files to 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor/target/classes
[INFO] [bundle:manifest {execution: bundle-manifest}]
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor/src/test/resources
[INFO] Copying 0 resource to META-INF
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 3 source files to 
/srv/gump/public/workspace/apache-commons/digester/annotations-processor/target/test-classes
>@org.apache.commons.digester3.annotations.rules.ObjectCreate(pattern="rss/channel")
>@org.apache.commons.digester3.annotations.rules.ObjectCreate(pattern="rss/channel/image")
>@org.apache.commons.digester3.annotations.rules.ObjectCreate(pattern="rss/channel/item")
>
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] error: Impossible to generate class 
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule: 
Attempt to recreate a file for type 
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule
[ERROR] error: Impossible to generate class 
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule: 
Attempt to recreate a file for type 
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule
[INFO] 2 errors 
[INFO] -
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure

error: Impossible to generate class 
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule: 
Attempt to recreate a file for type 
org.apache.commons.digester3.a

Re: Moving to svnpubsub for dist releases

[Emmanuel Bourg]

Le 26/11/2012 01:01, sebb a écrit :

> Hope this all makes sense!

Well, maybe I misunderstood, but committing the RC sites for review into
a SVN repository seems a bit convoluted to me. A good old upload on
people.apache.org was perfectly fine.

Emmanuel Bourg




smime.p7s
Description: Signature cryptographique S/MIME

Re: [VOTE] Release Apache Commons Daemon 1.0.11

[sebb]

On 22 November 2012 13:22, Mladen Turk  wrote:
> Apache Commons Daemon 1.0.11 based on RC1 is ready.
> Binaries and sources for testing are at [1], site can be
> found at [2]. Tag is [3] which will be renamed to COMMONS_DAEMON_1_0_11 if
> voted.
>
> Please vote (vote will remain open for at least 72 hours).
>
> Apache Commons Daemon 1.0.11 is
>   [X] +1 Release
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
>
> [1] http://people.apache.org/~mturk/daemon-1.0.11/
> [2] http://people.apache.org/~mturk/daemon-1.0.11-site/
> [3]
> https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_11_RC1/
>
>
> Regards
> --
> ^TM
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons Daemon 1.0.11

[luc]

Le 2012-11-22 14:22, Mladen Turk a écrit :

Apache Commons Daemon 1.0.11 based on RC1 is ready.
Binaries and sources for testing are at [1], site can be
found at [2]. Tag is [3] which will be renamed to
COMMONS_DAEMON_1_0_11 if voted.

Please vote (vote will remain open for at least 72 hours).

Apache Commons Daemon 1.0.11 is
  [X] +1 Release


Luc


  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...


[1] http://people.apache.org/~mturk/daemon-1.0.11/
[2] http://people.apache.org/~mturk/daemon-1.0.11-site/
[3]

https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_11_RC1/


Regards



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-io-test (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

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


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/io/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/io/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/gump_work/build_apache-commons_commons-io-test.html
Work Name: build_apache-commons_commons-io-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 6 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/io]
M2_HOME: /opt/maven2
-
Running org.apache.commons.io.comparator.CompositeFileComparatorTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.172 sec
Running org.apache.commons.io.comparator.DefaultFileComparatorTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.146 sec
Running org.apache.commons.io.comparator.DirectoryFileComparatorTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.161 sec
Running org.apache.commons.io.comparator.ExtensionFileComparatorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.166 sec
Running org.apache.commons.io.comparator.PathFileComparatorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec
Running org.apache.commons.io.comparator.NameFileComparatorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.184 sec
Running org.apache.commons.io.IOUtilsTestCase
Tests run: 63, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.815 sec
Running org.apache.commons.io.IOCaseTestCase
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.226 sec
Running org.apache.commons.io.LineIteratorTestCase
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.328 sec
Running org.apache.commons.io.FileUtilsCleanDirectoryTestCase
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.274 sec
Running org.apache.commons.io.IOUtilsWriteTestCase
Tests run: 53, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.458 sec
Running org.apache.commons.io.FilenameUtilsWildcardTestCase
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.257 sec
Running org.apache.commons.io.FileUtilsListFilesTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
Running org.apache.commons.io.FileSystemUtilsTestCase
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.438 sec
Running org.apache.commons.io.DirectoryWalkerTestCaseJava4
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.303 sec

Results :

Failed tests:   
testIO_356(org.apache.commons.io.input.CharSequenceInputStreamTest): 
bufferSize=10 dataSize=13: arrays first differed at element [0]; expected:<65> 
but was:<78>

Tests run: 985, Failures: 1, Errors: 0, Skipped: 1

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/srv/gump/public/workspace/apache-commons/io/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 2 minutes 4 seconds
[INFO] Finished at: Mon Nov 26 08:26:18 UTC 2012
[INFO] Final Memory: 37M/89M
[INFO] 
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/rss.xml
- Atom: 
http://vmgum

[GUMP@vmgump]: Project commons-exec-test (in module apache-commons) failed

[Gump]

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 gene...@gump.apache.org.

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


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/exec/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/gump_work/build_apache-commons_commons-exec-test.html
Work Name: build_apache-commons_commons-exec-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 29 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/exec]
M2_HOME: /opt/maven2
-
FOO..
gdal_translate
HDF5:"/home/kk/grass/data/4404.he5"://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif
FOO..
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.032 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.029 ms
Process completed in 2004 millis; below is its output
Process timed out and was killed by watchdog.
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
Process completed in 2004 millis; below is its output
Process timed out and was killed.
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Executing [sh, -c, src/test/scripts/invoker.sh]
invoker.sh -- going to start daemon process
invoker.sh --  daemon process was started
cd: 21: can't cd to ../../../target
Process completed in 8062 millis; above is its output
Processes terminated: 6 killed: 0 Multiplier: 1 MaxRetries: 180 Elapsed (avg 
ms): 1004
Tests run: 41, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.915 sec <<< 
FAILURE!
testExec_60(org.apache.commons.exec.DefaultExecutorTest)  Time elapsed: 6040 
sec  <<< FAILURE!
junit.framework.AssertionFailedError: Not a single process was killed by the 
watch dog
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at 
org.apache.commons.exec.DefaultExecutorTest.testExec_60(DefaultExecutorTest.java:1129)


Results :

Failed tests:   testExec_60(org.apache.commons.exec.DefaultExecutorTest): Not a 
single process was killed by the watch dog

Tests run: 96, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 minute 27 seconds
[INFO] Finished at: Mon Nov 26 08:22:03 UTC 2012
[INFO] Final Memory: 40M/95M
[INFO] 
-

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

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 07000626112012, vmgump.apache.org:vmgump:07000626112012
Gump E-mail Identifier (unique within run) #18.

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

---