Re: [Math] maven: Problem with "clirr"

[Damjan Jovanovic]

On Tue, Apr 24, 2012 at 11:19 PM, Gilles Sadowski
 wrote:
> Hi.
>
> Clirr now fails the build on error:
> ---CUT---
> [ERROR] Unable to find information in class 
> org.apache.commons.math3.linear.SymmLQ referring back to nested class 
> org.apache.commons.math3.linear.SymmLQ$SymmLQEvent
> [ERROR] Unable to find information in class 
> org.apache.commons.math3.optimization.direct.PowellOptimizer referring back 
> to nested class 
> org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
> ---CUT---
>
> Since I don't know what causes those errors, I'd like to be able to skip
> the "clirr" check altogether.

It seems you got lucky, that error used to break the build until very
recently (http://jira.codehaus.org/browse/MCLIRR-36).

Clirr is old, and I think it only works properly with Java 1.4, it
can't handle some aspects of the new .class file format from later
versions.

Damjan

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

Re: [PARENT] release of pom packaging project fails jar plugin

[sebb]

On 25 April 2012 07:48, Jörg Schaible  wrote:
> Michael Heuer wrote:
>
>> Jörg Schaible wrote:
>>> Michael Heuer wrote:
>>>
 I'm forwarding this message originally sent to users@maven that
 received no response.  Perhaps dev@commons is more appropriate.
>>>
>>> why do you think, that extending from Apache Commons parent is a good
>>> thing? This parent is crafted so that it fits exactly our (Apache
>>> Commons) needs. It is considered internal and is not designed to work for
>>> all cases (especially outside its environment).
>>>
>>> Said that, if you provide patches for this POM that have no side-effects
>>> for all our components, we might consider to apply them, but don't expect
>>> that someone is maintaining/developing this parent POM like any other
>>> Commons component.
>>>
>>> IMHO, you're better off if you copy the interesting parts into a shared
>>> parent of your own.
>>
>> Thank you for the response, Jörg.
>>
>> That is what I have done, copy the interesting bits from the commons
>> and Apache parents into our internal parent.  We're not extending from
>> either.
>>
>> I'm not seeing how the commons parent with its release profiles can
>> work for pom packaging projects (such as the parent project or
>> multimodule projects).  When commons-parent is released, are none of
>> the release profiles enabled (rc, release, apache-release)?
>
> - rc: the one we use

That was the one we used for creating RCs prior to Nexus.

> - release: automatically activated by M2 (IIRC)

This is the one I normally use.

I think rc and release are fairly similar.

However, I'm not sure either can be used for releasing the parent POM.

> - apache-release: outdated?

This is the one in the ASF pom; IIRC it clashes with our requirements.

>> Are any
>> of the commons projects currently multimodule builds?
>
> http://wiki.apache.org/commons/CreatingReleases
>
> vfs is a multi-project
>
> - Jörg
>
>
> -
> 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: [Math] maven: Problem with "clirr"

[sebb]

On 25 April 2012 09:12, Damjan Jovanovic  wrote:
> On Tue, Apr 24, 2012 at 11:19 PM, Gilles Sadowski
>  wrote:
>> Hi.
>>
>> Clirr now fails the build on error:
>> ---CUT---
>> [ERROR] Unable to find information in class 
>> org.apache.commons.math3.linear.SymmLQ referring back to nested class 
>> org.apache.commons.math3.linear.SymmLQ$SymmLQEvent
>> [ERROR] Unable to find information in class 
>> org.apache.commons.math3.optimization.direct.PowellOptimizer referring back 
>> to nested class 
>> org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
>> ---CUT---
>>
>> Since I don't know what causes those errors, I'd like to be able to skip
>> the "clirr" check altogether.
>
> It seems you got lucky, that error used to break the build until very
> recently (http://jira.codehaus.org/browse/MCLIRR-36).
>
> Clirr is old, and I think it only works properly with Java 1.4, it
> can't handle some aspects of the new .class file format from later
> versions.

Generally works fine for me with Oracle/Sun Java, but using the
Eclipse compiler causes problems.

I've just tried with Math trunk, and

mvn clean clirr:clirr

works fine with Java 1.5 and 1.6 and 1.7

> Damjan
>
> -
> 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: [Math] maven: Problem with "clirr"

[Gilles Sadowski]

On Wed, Apr 25, 2012 at 12:53:46AM +0100, sebb wrote:
> On 24 April 2012 22:19, Gilles Sadowski  wrote:
> > Hi.
> >
> > Clirr now fails the build on error:
> > ---CUT---
> > [ERROR] Unable to find information in class 
> > org.apache.commons.math3.linear.SymmLQ referring back to nested class 
> > org.apache.commons.math3.linear.SymmLQ$SymmLQEvent
> > [ERROR] Unable to find information in class 
> > org.apache.commons.math3.optimization.direct.PowellOptimizer referring back 
> > to nested class 
> > org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
> > ---CUT---
> >
> > Since I don't know what causes those errors, I'd like to be able to skip
> > the "clirr" check altogether.
> 
> Clirr does not like the output from the Eclipse compiler.
> Make sure you run mvn clean first - and ensure that Eclipse is not set
> to build the project.
> 
> > I tried to mimic settings suggested in an earlier messafe about skipping
> > lengthy report, i.e.
> >   true
> 
> AFAIK, that's not the same as setting a command-line property.

This syntax worked for other reports (you suggested it).

> 
> > It didn't work.
> >
> > I tried this:
> >  false
> > as documented here:
> >  http://clirr.sourceforge.net/clirr-maven/properties.html
> 
> That is for an obsolete version of the Clirr plugin
> 
> The current version is documented at:
> 
> http://mojo.codehaus.org/clirr-maven-plugin/

The usage page there is rather terse, there is no information about
which properties could alter the behaviour of the plugin (like disabling it,
making just a warning, not a error that fails the build).

> 
> > It didn't work.
> >
> 
> mvn  -Dclirr.skip
> 
> works for me.

Doesn't work here! Using:

$ mvn -version
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.7.0_03-icedtea, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-5-vserver-amd64", arch: "amd64", family: 
"unix"


Gilles

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

Re: [PARENT] release of pom packaging project fails jar plugin

[Jörg Schaible]

Hi Sebb,

sebb wrote:

> On 25 April 2012 07:48, Jörg Schaible  wrote:

[snip]

>> - rc: the one we use
> 
> That was the one we used for creating RCs prior to Nexus.
> 
>> - release: automatically activated by M2 (IIRC)
> 
> This is the one I normally use.
> 
> I think rc and release are fairly similar.

Well, the profile "release" is activated by the plugin as default, see 
(default) configuration of the release plugin. As long as no-one overwrites 
the setting ... ;-)

> However, I'm not sure either can be used for releasing the parent POM.

"release" (resp. the configured ones) should be active nevertheless, you may 
add more using -P option.

>> - apache-release: outdated?
> 
> This is the one in the ASF pom; IIRC it clashes with our requirements.

OK.

>>> Are any
>>> of the commons projects currently multimodule builds?
>>
>> http://wiki.apache.org/commons/CreatingReleases

We should finalize it. Gary, did you follow now that steps?

And we must update or drop http://commons.apache.org/releases/index.html

Cheers,
Jörg


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

[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)

[Continuum@vmbuild]

Online report : 
http://vmbuild.apache.org/continuum/buildResult.action?buildId=21497&projectId=73

Build statistics:
  State: Failed
  Previous State: Ok
  Started at: Wed 25 Apr 2012 10:24:51 +
  Finished at: Wed 25 Apr 2012 10:25:55 +
  Total time: 1m 3s
  Build Trigger: Schedule
  Build Number: 108
  Exit code: 1
  Building machine hostname: vmbuild
  Operating system : Linux(unknown)
  Java Home version : 
  java version "1.6.0_30"
  Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
  Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)

  Builder version :
  Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+)
  Java version: 1.6.0_30
  Java home: /usr/lib/jvm/jdk1.6.0_30/jre
  Default locale: en_US, platform encoding: ANSI_X3.4-1968
  OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: 
"unix"


SCM Changes:

Changed: markt @ Wed 25 Apr 2012 09:49:22 +
Comment: Updates for maxWait -> maxWaitMillis
Files changed:
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/BasicDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/BasicDataSourceFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/PoolableConnectionFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/cpdsadapter/DriverAdapterCPDS.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/PerUserPoolDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/PerUserPoolDataSourceFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/SharedPoolDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/SharedPoolDataSourceFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/managed/PoolableManagedConnectionFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/TestBasicDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/TestBasicDataSourceFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/TestPoolingDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/TestPoolingDriver.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/datasources/TestCPDSConnectionFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/datasources/TestKeyedCPDSConnectionFactory.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/datasources/TestPerUserPoolDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/datasources/TestSharedPoolDataSource.java
 ( 1330174 )
  
/commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp2/managed/TestManagedDataSource.java
 ( 1330174 )


Dependencies Changes:

org.apache.commons:commons-pool2:2.0-SNAPSHOT



Build Definition:

POM filename: pom.xml
Goals: clean deploy   
Arguments: --batch-mode
Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: COMMONS_SCHEDULE
Profile Name: Maven 2.2.1
Description: Default Maven 2 Build Definition (Java 1.6)


Test Summary:

Tests: 443
Failures: 1
Errors: 0
Success Rate: 99
Total time: 46.328003


Test Failures:


TestBasicDataSourceFactory
testProperties :
  junit.framework.AssertionFailedError
  junit.framework.AssertionFailedError: expected:<500> but was:<-1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:130)
at junit.framework.Assert.assertEquals(Assert.java:136)
at 
org.apache.commons.dbcp2.TestBasicDataSourceFactory.testProperties(TestBasicDataSourceFactory.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invo

Re: [Math] maven: Problem with "clirr"

[Jörg Schaible]

Gilles Sadowski wrote:

> On Wed, Apr 25, 2012 at 12:53:46AM +0100, sebb wrote:
>> On 24 April 2012 22:19, Gilles Sadowski 
>> wrote:
>> > Hi.
>> >
>> > Clirr now fails the build on error:
>> > ---CUT---
>> > [ERROR] Unable to find information in class
>> > [org.apache.commons.math3.linear.SymmLQ referring back to nested class
>> > [org.apache.commons.math3.linear.SymmLQ$SymmLQEvent ERROR] Unable to
>> > [find information in class
>> > [org.apache.commons.math3.optimization.direct.PowellOptimizer referring
>> > [back to nested class
>> > 
[org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
>> > ---CUT---
>> >
>> > Since I don't know what causes those errors, I'd like to be able to
>> > skip the "clirr" check altogether.
>> 
>> Clirr does not like the output from the Eclipse compiler.
>> Make sure you run mvn clean first - and ensure that Eclipse is not set
>> to build the project.
>> 
>> > I tried to mimic settings suggested in an earlier messafe about
>> > skipping lengthy report, i.e.
>> > true
>> 
>> AFAIK, that's not the same as setting a command-line property.
> 
> This syntax worked for other reports (you suggested it).
> 
>> 
>> > It didn't work.
>> >
>> > I tried this:
>> > false
>> > as documented here:
>> > http://clirr.sourceforge.net/clirr-maven/properties.html
>> 
>> That is for an obsolete version of the Clirr plugin
>> 
>> The current version is documented at:
>> 
>> http://mojo.codehaus.org/clirr-maven-plugin/
> 
> The usage page there is rather terse, there is no information about
> which properties could alter the behaviour of the plugin (like disabling
> it, making just a warning, not a error that fails the build).

The properties from command line should be the ones used in "Expression:" 
http://mojo.codehaus.org/clirr-maven-plugin/check-mojo.html

>> > It didn't work.
>> >
>> 
>> mvn  -Dclirr.skip
>> 
>> works for me.
> 
> Doesn't work here! Using:
> 
> $ mvn -version
> Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.7.0_03-icedtea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-5-vserver-amd64", arch: "amd64",
> family: "unix"

Can you try with M221? Maybe the system property is no longer passed to the 
forked process ... :-/
Or try to use the check-no-fork goal instead.

- Jörg


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

Re: [PARENT] release of pom packaging project fails jar plugin

[Gary Gregory]

On Apr 25, 2012, at 6:19, "Jörg Schaible"  wrote:

> Hi Sebb,
>
> sebb wrote:
>
>> On 25 April 2012 07:48, Jörg Schaible  wrote:
>
> [snip]
>
>>> - rc: the one we use
>>
>> That was the one we used for creating RCs prior to Nexus.
>>
>>> - release: automatically activated by M2 (IIRC)
>>
>> This is the one I normally use.
>>
>> I think rc and release are fairly similar.
>
> Well, the profile "release" is activated by the plugin as default, see
> (default) configuration of the release plugin. As long as no-one overwrites
> the setting ... ;-)
>
>> However, I'm not sure either can be used for releasing the parent POM.
>
> "release" (resp. the configured ones) should be active nevertheless, you may
> add more using -P option.
>
>>> - apache-release: outdated?
>>
>> This is the one in the ASF pom; IIRC it clashes with our requirements.
>
> OK.
>
 Are any
 of the commons projects currently multimodule builds?
>>>
>>> http://wiki.apache.org/commons/CreatingReleases
>
> We should finalize it. Gary, did you follow now that steps?

No, I use http://wiki.apache.org/commons/UsingNexus

Gary

>
> And we must update or drop http://commons.apache.org/releases/index.html
>
> Cheers,
> Jörg
>
>
> -
> 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: [Math] maven: Problem with "clirr"

[Jochen Wiedmann]

Is the next version of Math expected  to be binary compatible with the
previous. If so, we should take this serious. Otherwise, we should
possibly disable clirr for now, for example by enabling it in the
release- and rc-profiles only.


On Wed, Apr 25, 2012 at 12:06 PM, Gilles Sadowski
 wrote:
> On Wed, Apr 25, 2012 at 12:53:46AM +0100, sebb wrote:
>> On 24 April 2012 22:19, Gilles Sadowski  wrote:
>> > Hi.
>> >
>> > Clirr now fails the build on error:
>> > ---CUT---
>> > [ERROR] Unable to find information in class 
>> > org.apache.commons.math3.linear.SymmLQ referring back to nested class 
>> > org.apache.commons.math3.linear.SymmLQ$SymmLQEvent
>> > [ERROR] Unable to find information in class 
>> > org.apache.commons.math3.optimization.direct.PowellOptimizer referring 
>> > back to nested class 
>> > org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
>> > ---CUT---
>> >
>> > Since I don't know what causes those errors, I'd like to be able to skip
>> > the "clirr" check altogether.
>>
>> Clirr does not like the output from the Eclipse compiler.
>> Make sure you run mvn clean first - and ensure that Eclipse is not set
>> to build the project.
>>
>> > I tried to mimic settings suggested in an earlier messafe about skipping
>> > lengthy report, i.e.
>> >   true
>>
>> AFAIK, that's not the same as setting a command-line property.
>
> This syntax worked for other reports (you suggested it).
>
>>
>> > It didn't work.
>> >
>> > I tried this:
>> >  false
>> > as documented here:
>> >  http://clirr.sourceforge.net/clirr-maven/properties.html
>>
>> That is for an obsolete version of the Clirr plugin
>>
>> The current version is documented at:
>>
>> http://mojo.codehaus.org/clirr-maven-plugin/
>
> The usage page there is rather terse, there is no information about
> which properties could alter the behaviour of the plugin (like disabling it,
> making just a warning, not a error that fails the build).
>
>>
>> > It didn't work.
>> >
>>
>> mvn  -Dclirr.skip
>>
>> works for me.
>
> Doesn't work here! Using:
>
> $ mvn -version
> Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.7.0_03-icedtea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-5-vserver-amd64", arch: "amd64", family: 
> "unix"
>
>
> Gilles
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>



-- 
"Bildung kommt von Bildschirm und nicht von Buch, sonst hieße es ja Buchung."
Dieter Hildebrandt

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

Re: [PARENT] release of pom packaging project fails jar plugin

[sebb]

On 25 April 2012 11:18, Jörg Schaible  wrote:
> Hi Sebb,
>
> sebb wrote:
>
>> On 25 April 2012 07:48, Jörg Schaible  wrote:
>
> [snip]
>
>>> - rc: the one we use
>>
>> That was the one we used for creating RCs prior to Nexus.
>>
>>> - release: automatically activated by M2 (IIRC)
>>
>> This is the one I normally use.
>>
>> I think rc and release are fairly similar.
>
> Well, the profile "release" is activated by the plugin as default, see
> (default) configuration of the release plugin. As long as no-one overwrites
> the setting ... ;-)

I don't use the release plugin, because I don't like the way it messes
with trunk.
I prefer to create the tag from clean trunk checkout + version updates.
Much safer that way.

>> However, I'm not sure either can be used for releasing the parent POM.
>
> "release" (resp. the configured ones) should be active nevertheless, you may
> add more using -P option.
>
>>> - apache-release: outdated?
>>
>> This is the one in the ASF pom; IIRC it clashes with our requirements.
>
> OK.
>
 Are any
 of the commons projects currently multimodule builds?
>>>
>>> http://wiki.apache.org/commons/CreatingReleases
>
> We should finalize it. Gary, did you follow now that steps?
>
> And we must update or drop http://commons.apache.org/releases/index.html

Yes.

> Cheers,
> Jörg
>
>
> -
> 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: [Math] maven: Problem with "clirr"

[Gilles Sadowski]

Hi.

> >> >
> >> > Clirr now fails the build on error:
> >> > ---CUT---
> >> > [ERROR] Unable to find information in class
> >> > [org.apache.commons.math3.linear.SymmLQ referring back to nested class
> >> > [org.apache.commons.math3.linear.SymmLQ$SymmLQEvent ERROR] Unable to
> >> > [find information in class
> >> > [org.apache.commons.math3.optimization.direct.PowellOptimizer referring
> >> > [back to nested class
> >> > 
> [org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
> >> > ---CUT---
> >> >
> >> > Since I don't know what causes those errors, I'd like to be able to
> >> > skip the "clirr" check altogether.
> >> 
> >> Clirr does not like the output from the Eclipse compiler.
> >> Make sure you run mvn clean first - and ensure that Eclipse is not set
> >> to build the project.
> >> 
> >> > I tried to mimic settings suggested in an earlier messafe about
> >> > skipping lengthy report, i.e.
> >> > true
> >> 
> >> AFAIK, that's not the same as setting a command-line property.
> > 
> > This syntax worked for other reports (you suggested it).
> > 
> >> 
> >> > It didn't work.
> >> >
> >> > I tried this:
> >> > false
> >> > as documented here:
> >> > http://clirr.sourceforge.net/clirr-maven/properties.html
> >> 
> >> That is for an obsolete version of the Clirr plugin
> >> 
> >> The current version is documented at:
> >> 
> >> http://mojo.codehaus.org/clirr-maven-plugin/
> > 
> > The usage page there is rather terse, there is no information about
> > which properties could alter the behaviour of the plugin (like disabling
> > it, making just a warning, not a error that fails the build).
> 
> The properties from command line should be the ones used in "Expression:" 
> http://mojo.codehaus.org/clirr-maven-plugin/check-mojo.html

Thanks.
I tried "failOnError" set to "false". Didn't work.

Here the stack trace from maven output:
---CUT---
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
project commons-math3: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
project commons-math3: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site 
failed: 780
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 780
at 
org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:666)
at 
org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:679)
at 
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:263)
at org.codehaus.mojo.clirr.ClirrReport.doReport(ClirrReport.java:243)
at org.codehaus.mojo.clirr.ClirrReport.generat

Re: [PARENT] release of pom packaging project fails jar plugin

[Jörg Schaible]

sebb wrote:

> On 25 April 2012 11:18, Jörg Schaible  wrote:
>> Hi Sebb,
>>
>> sebb wrote:
>>
>>> On 25 April 2012 07:48, Jörg Schaible 
>>> wrote:
>>
>> [snip]
>>
 - rc: the one we use
>>>
>>> That was the one we used for creating RCs prior to Nexus.
>>>
 - release: automatically activated by M2 (IIRC)
>>>
>>> This is the one I normally use.
>>>
>>> I think rc and release are fairly similar.
>>
>> Well, the profile "release" is activated by the plugin as default, see
>> (default) configuration of the release plugin. As long as no-one
>> overwrites the setting ... ;-)
> 
> I don't use the release plugin, because I don't like the way it messes
> with trunk.

You mean the two commits for the "final" POM and its immediate update?

> I prefer to create the tag from clean trunk checkout + version updates.
> Much safer that way.

The plugin takes care for all the version updates ... seems we have 
different preferences here :)

[snip]

- Jörg


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

Re: [PARENT] release of pom packaging project fails jar plugin

[sebb]

On 25 April 2012 14:08, Jörg Schaible  wrote:
> sebb wrote:
>
>> On 25 April 2012 11:18, Jörg Schaible  wrote:
>>> Hi Sebb,
>>>
>>> sebb wrote:
>>>
 On 25 April 2012 07:48, Jörg Schaible 
 wrote:
>>>
>>> [snip]
>>>
> - rc: the one we use

 That was the one we used for creating RCs prior to Nexus.

> - release: automatically activated by M2 (IIRC)

 This is the one I normally use.

 I think rc and release are fairly similar.
>>>
>>> Well, the profile "release" is activated by the plugin as default, see
>>> (default) configuration of the release plugin. As long as no-one
>>> overwrites the setting ... ;-)
>>
>> I don't use the release plugin, because I don't like the way it messes
>> with trunk.
>
> You mean the two commits for the "final" POM and its immediate update?
>
>> I prefer to create the tag from clean trunk checkout + version updates.
>> Much safer that way.
>
> The plugin takes care for all the version updates ... seems we have
> different preferences here :)

The advantage of the manual method is that there is no need to revert
trunk if the RC fails.
The SVN commit messages are also cleaner IMO.

> [snip]
>
> - Jörg
>
>
> -
> 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: [Math] Question about "AbstractLeastSquaresOptimizer" code

[Gilles Sadowski]

Hi.

> looking at various references, it seems that the definition of the error as
> errors[i] = FastMath.sqrt(covar[i][i]) * c;
> or
> errors[i] = FastMath.sqrt(covar[i][i]);
> is a matter of convention.
> 
> I'm no statistician, but I gathered that the first expression is what
> is called Asymptotic Standard Error (see equations 34 and 35,
> http://mathworld.wolfram.com/LeastSquaresFitting.html). Meanwhile, NR
> seems to favor the second expression. It would be nice to check what R
> (which is truly statistician's stuff) returns as parameters errors.

Thanks for looking into that.

Can we then agree that the current naming is not really clear?
Since we are not allowed to readily remove this method, the best solution
would be to update the Javadoc to make it clear what is done there, i.e.
cite the full definition of ASE (together with a reference).

Then, to further disambiguate, we could add a
  double[] getSigma()
method that will in effect return the (sqrt of the) diagonal elements of the
covariance matrix.

Is that OK?
If so, would you take care of that, Sébastien?


Thanks,
Gilles

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

Re: [Math] maven: Problem with "clirr"

[sebb]

On 25 April 2012 13:36, Gilles Sadowski  wrote:
> Hi.
>
>> >> >
>> >> > Clirr now fails the build on error:
>> >> > ---CUT---
>> >> > [ERROR] Unable to find information in class
>> >> > [org.apache.commons.math3.linear.SymmLQ referring back to nested class
>> >> > [org.apache.commons.math3.linear.SymmLQ$SymmLQEvent ERROR] Unable to
>> >> > [find information in class
>> >> > [org.apache.commons.math3.optimization.direct.PowellOptimizer referring
>> >> > [back to nested class
>> >> >
>> [org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
>> >> > ---CUT---
>> >> >
>> >> > Since I don't know what causes those errors, I'd like to be able to
>> >> > skip the "clirr" check altogether.
>> >>
>> >> Clirr does not like the output from the Eclipse compiler.
>> >> Make sure you run mvn clean first - and ensure that Eclipse is not set
>> >> to build the project.
>> >>
>> >> > I tried to mimic settings suggested in an earlier messafe about
>> >> > skipping lengthy report, i.e.
>> >> > true
>> >>
>> >> AFAIK, that's not the same as setting a command-line property.
>> >
>> > This syntax worked for other reports (you suggested it).
>> >
>> >>
>> >> > It didn't work.
>> >> >
>> >> > I tried this:
>> >> > false
>> >> > as documented here:
>> >> > http://clirr.sourceforge.net/clirr-maven/properties.html
>> >>
>> >> That is for an obsolete version of the Clirr plugin
>> >>
>> >> The current version is documented at:
>> >>
>> >> http://mojo.codehaus.org/clirr-maven-plugin/
>> >
>> > The usage page there is rather terse, there is no information about
>> > which properties could alter the behaviour of the plugin (like disabling
>> > it, making just a warning, not a error that fails the build).
>>
>> The properties from command line should be the ones used in "Expression:"
>> http://mojo.codehaus.org/clirr-maven-plugin/check-mojo.html
>
> Thanks.
> I tried "failOnError" set to "false". Didn't work.
>
> Here the stack trace from maven output:
> ---CUT---
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project commons-math3: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project commons-math3: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780
>        at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>        at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>        at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>        at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>        at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>        at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>        at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>        at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:601)
>        at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>        at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>        at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>        at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site 
> failed: 780
>        at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>        at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>        ... 19 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 780
>        at 
> org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:666)
>        at 
> org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:679)
>        at 
> org.codehaus.mojo.clirr.AbstractC

Re: [Math] Question about "AbstractLeastSquaresOptimizer" code

[Sébastien Brisard]

Hi Gillles,
>
> Can we then agree that the current naming is not really clear?
> Since we are not allowed to readily remove this method, the best solution
> would be to update the Javadoc to make it clear what is done there, i.e.
> cite the full definition of ASE (together with a reference).
>
this would be the best solution in my view. I just need to find a good
reference where ASE is properly defined.

> Then, to further disambiguate, we could add a
>  double[] getSigma()
> method that will in effect return the (sqrt of the) diagonal elements of the
> covariance matrix.
>
> Is that OK?
> If so, would you take care of that, Sébastien?
>
Will gladly do so!

Sébastien


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

[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.
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 23 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
-
Running org.apache.commons.exec.util.StringUtilTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.commons.exec.util.MapUtilTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.exec.DefaultExecutorTest
FOO..
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
Process completed in 2012 millis; below is its output
Process timed out and was killed.
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 8056 millis; above is its output
Processes terminated: 6 killed: 0 Multiplier: 1 MaxRetries: 180 Elapsed (avg 
ms): 1008
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
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.022 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.031 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.028 ms
Process completed in 2005 millis; below is its output
Process timed out and was killed by watchdog.
gdal_translate
HDF5:"/home/kk/grass/data/4404.he5"://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif
FOO..
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.914 sec <<< 
FAILURE!

Results :

Failed tests: 
  testExec_60(org.apache.commons.exec.DefaultExecutorTest)

Tests run: 95, 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 22 seconds
[INFO] Finished at: Wed Apr 25 13:58:59 UTC 2012
[INFO] Final Memory: 25M/65M
[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 06001225042012, vmgump.apache.org:vmgump:06001225042012
Gump E-mail Identifier (unique within run) #1.

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

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

Re: [Math] maven: Problem with "clirr"

[Sébastien Brisard]

>
> Have you tried Maven 221?
>
I'm using maven 2.2.1, and no such error occurs! I do get a report,
with a lot of complaints regarding the geometry package.

> Have you tried
>
> mvn clean clirr:clirr ?
>
>> In the meantime, I'd be glad to be able to disable this tool... :-{
>
> -1, because Math needs to preserve binary compat.
>
I'm the culprit for breaking binary compatibility. But for my defense,
the clirr report generated by maven 2.2.1 does not complain about the
removal of this private nested class.

Sébastien


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

Re: [Math] maven: Problem with "clirr"

[Gilles Sadowski]

Hi.

> >
> > Does anyone have an idea of what can cause this?
> 
> Have you tried Maven 221?

No.

> 
> Have you tried
> 
> mvn clean clirr:clirr ?

That was the trick. Thanks.
Sorry; I still have a hard time understanding when the "clean" becomes a
necessary step!

> 
> > In the meantime, I'd be glad to be able to disable this tool... :-{
> 
> -1, because Math needs to preserve binary compat.

As before, this was a request as to how locally skip the report generation,
not that it should be part of the policy...

With

 $ mvn clean clirr:clirr -Dclirr.skip=true

the report is skipped, but with

 $ mvn clean -Pquick-report -Dclirr.skip=true site

it is not skipped. The logic behind this behaviour evades me...

Anyway, it turns out there was no compatibility error, just a glitch that
made it look like it.


Regards,
Gilles

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

Re: [Math] maven: Problem with "clirr"

[Gilles Sadowski]

On Wed, Apr 25, 2012 at 04:00:30PM +0200, Sébastien Brisard wrote:
> >
> > Have you tried Maven 221?
> >
> I'm using maven 2.2.1, and no such error occurs! I do get a report,
> with a lot of complaints regarding the geometry package.
> 
> > Have you tried
> >
> > mvn clean clirr:clirr ?
> >
> >> In the meantime, I'd be glad to be able to disable this tool... :-{
> >
> > -1, because Math needs to preserve binary compat.
> >
> I'm the culprit for breaking binary compatibility. But for my defense,
> the clirr report generated by maven 2.2.1 does not complain about the
> removal of this private nested class.

No, you are not guilty; there was no crime after all. :-)
[Just an erratic plugin...]


Best,
Gilles

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

Re: [Math] Question about "AbstractLeastSquaresOptimizer" code

[Gilles Sadowski]

On Wed, Apr 25, 2012 at 03:46:58PM +0200, Sébastien Brisard wrote:
> Hi Gillles,
> >
> > Can we then agree that the current naming is not really clear?
> > Since we are not allowed to readily remove this method, the best solution
> > would be to update the Javadoc to make it clear what is done there, i.e.
> > cite the full definition of ASE (together with a reference).
> >
> this would be the best solution in my view. I just need to find a good
> reference where ASE is properly defined.

The ones you found are good enough, I guess; just to let people know that
they might not want to use that method. ;-)

> 
> > Then, to further disambiguate, we could add a
> >  double[] getSigma()
> > method that will in effect return the (sqrt of the) diagonal elements of the
> > covariance matrix.
> >
> > Is that OK?
> > If so, would you take care of that, Sébastien?
> >
> Will gladly do so!

Thanks,
Gilles

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

Re: [Math] Question about "AbstractLeastSquaresOptimizer" code

[Sébastien Brisard]

2012/4/25 Gilles Sadowski :
> On Wed, Apr 25, 2012 at 03:46:58PM +0200, Sébastien Brisard wrote:
>> Hi Gillles,
>> >
>> > Can we then agree that the current naming is not really clear?
>> > Since we are not allowed to readily remove this method, the best solution
>> > would be to update the Javadoc to make it clear what is done there, i.e.
>> > cite the full definition of ASE (together with a reference).
>> >
>> this would be the best solution in my view. I just need to find a good
>> reference where ASE is properly defined.
>
> The ones you found are good enough, I guess; just to let people know that
> they might not want to use that method. ;-)
>
Oh no, they do want to use this method. From what I gathered, it's
actually the standard way of estimating the error on the parameters. I
found two nice references
1. http://www.itl.nist.gov/div898/strd/ (NIST is your friend -- will
implement some unit tests based on these reference cases!)
2. http://en.wikipedia.org/wiki/Least_squares see paragraph "In a
least squares calculation with unit weights, or in linear regression,
the variance on the jth parameter"

Best regards,
Sébastien


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

Re: [PARENT] release of pom packaging project fails jar plugin

[Michael Heuer]

On Wed, Apr 25, 2012 at 4:03 AM, sebb  wrote:
> On 25 April 2012 07:48, Jörg Schaible  wrote:
>> Michael Heuer wrote:
>>
>>> Jörg Schaible wrote:
 Michael Heuer wrote:

> I'm forwarding this message originally sent to users@maven that
> received no response.  Perhaps dev@commons is more appropriate.

 why do you think, that extending from Apache Commons parent is a good
 thing? This parent is crafted so that it fits exactly our (Apache
 Commons) needs. It is considered internal and is not designed to work for
 all cases (especially outside its environment).

 Said that, if you provide patches for this POM that have no side-effects
 for all our components, we might consider to apply them, but don't expect
 that someone is maintaining/developing this parent POM like any other
 Commons component.

 IMHO, you're better off if you copy the interesting parts into a shared
 parent of your own.
>>>
>>> Thank you for the response, Jörg.
>>>
>>> That is what I have done, copy the interesting bits from the commons
>>> and Apache parents into our internal parent.  We're not extending from
>>> either.
>>>
>>> I'm not seeing how the commons parent with its release profiles can
>>> work for pom packaging projects (such as the parent project or
>>> multimodule projects).  When commons-parent is released, are none of
>>> the release profiles enabled (rc, release, apache-release)?
>>
>> - rc: the one we use
>
> That was the one we used for creating RCs prior to Nexus.
>
>> - release: automatically activated by M2 (IIRC)
>
> This is the one I normally use.
>
> I think rc and release are fairly similar.
>
> However, I'm not sure either can be used for releasing the parent POM.

I checked the newer documentation referenced in this thread

http://wiki.apache.org/commons/UsingNexus
http://www.apache.org/dev/publishing-maven-artifacts.html

and found this:

For Commons Parent, you can do:

$ mvn clean gpg:sign deploy -Ptest-deploy


I didn't see any explicit documentation about the actual release of
Parent to the Nexus staging directory, so I assume it is just

$ mvn gpg:sign deploy

?


>> - apache-release: outdated?
>
> This is the one in the ASF pom; IIRC it clashes with our requirements.
>
>>> Are any
>>> of the commons projects currently multimodule builds?
>>
>> http://wiki.apache.org/commons/CreatingReleases
>>
>> vfs is a multi-project

If I run

$ mvn clean deploy -Prelease -Ptest-deploy

on a fresh checkout of commons-vfs2-project it fails with

[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Commons VFS ... FAILURE [1:20.632s]
[INFO] Commons VFS Core .. SKIPPED
[INFO] Commons VFS Examples .. SKIPPED
[INFO] Commons VFS Distribution .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1:23.425s
[INFO] Finished at: Wed Apr 25 11:48:18 CDT 2012
[INFO] Final Memory: 15M/81M
[INFO] 
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
on project commons-vfs2-project: Error reading assemblies: No assembly
descriptors found. -> [Help 1]

   michael

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

Re: [PARENT] release of pom packaging project fails jar plugin

[sebb]

On 25 April 2012 17:54, Michael Heuer  wrote:
> On Wed, Apr 25, 2012 at 4:03 AM, sebb  wrote:
>> On 25 April 2012 07:48, Jörg Schaible  wrote:
>>> Michael Heuer wrote:
>>>
 Jörg Schaible wrote:
> Michael Heuer wrote:
>
>> I'm forwarding this message originally sent to users@maven that
>> received no response.  Perhaps dev@commons is more appropriate.
>
> why do you think, that extending from Apache Commons parent is a good
> thing? This parent is crafted so that it fits exactly our (Apache
> Commons) needs. It is considered internal and is not designed to work for
> all cases (especially outside its environment).
>
> Said that, if you provide patches for this POM that have no side-effects
> for all our components, we might consider to apply them, but don't expect
> that someone is maintaining/developing this parent POM like any other
> Commons component.
>
> IMHO, you're better off if you copy the interesting parts into a shared
> parent of your own.

 Thank you for the response, Jörg.

 That is what I have done, copy the interesting bits from the commons
 and Apache parents into our internal parent.  We're not extending from
 either.

 I'm not seeing how the commons parent with its release profiles can
 work for pom packaging projects (such as the parent project or
 multimodule projects).  When commons-parent is released, are none of
 the release profiles enabled (rc, release, apache-release)?
>>>
>>> - rc: the one we use
>>
>> That was the one we used for creating RCs prior to Nexus.
>>
>>> - release: automatically activated by M2 (IIRC)
>>
>> This is the one I normally use.
>>
>> I think rc and release are fairly similar.
>>
>> However, I'm not sure either can be used for releasing the parent POM.
>
> I checked the newer documentation referenced in this thread
>
> http://wiki.apache.org/commons/UsingNexus
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> and found this:
>
> For Commons Parent, you can do:
>
> $ mvn clean gpg:sign deploy -Ptest-deploy
>
>
> I didn't see any explicit documentation about the actual release of
> Parent to the Nexus staging directory, so I assume it is just
>
> $ mvn gpg:sign deploy
>

Yes

>
>
>>> - apache-release: outdated?
>>
>> This is the one in the ASF pom; IIRC it clashes with our requirements.
>>
 Are any
 of the commons projects currently multimodule builds?
>>>
>>> http://wiki.apache.org/commons/CreatingReleases
>>>
>>> vfs is a multi-project
>
> If I run
>
> $ mvn clean deploy -Prelease -Ptest-deploy
>
> on a fresh checkout of commons-vfs2-project it fails with
>
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Commons VFS ... FAILURE [1:20.632s]
> [INFO] Commons VFS Core .. SKIPPED
> [INFO] Commons VFS Examples .. SKIPPED
> [INFO] Commons VFS Distribution .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1:23.425s
> [INFO] Finished at: Wed Apr 25 11:48:18 CDT 2012
> [INFO] Final Memory: 15M/81M
> [INFO] 
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
> on project commons-vfs2-project: Error reading assemblies: No assembly
> descriptors found. -> [Help 1]

As the error message says - there are no assembly descriptors for the
parent POM.

>   michael
>
> -
> 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: [PARENT] release of pom packaging project fails jar plugin

[Ralph Goers]

For testing I've run mvn -P release clean install.  The deploy happens when I 
use the prepare and perform goals of the release plugin.

Ralph

Sent from my iPad

On Apr 25, 2012, at 9:54 AM, Michael Heuer  wrote:

> On Wed, Apr 25, 2012 at 4:03 AM, sebb  wrote:
>> On 25 April 2012 07:48, Jörg Schaible  wrote:
>>> Michael Heuer wrote:
>>> 
 Jörg Schaible wrote:
> Michael Heuer wrote:
> 
>> I'm forwarding this message originally sent to users@maven that
>> received no response.  Perhaps dev@commons is more appropriate.
> 
> why do you think, that extending from Apache Commons parent is a good
> thing? This parent is crafted so that it fits exactly our (Apache
> Commons) needs. It is considered internal and is not designed to work for
> all cases (especially outside its environment).
> 
> Said that, if you provide patches for this POM that have no side-effects
> for all our components, we might consider to apply them, but don't expect
> that someone is maintaining/developing this parent POM like any other
> Commons component.
> 
> IMHO, you're better off if you copy the interesting parts into a shared
> parent of your own.
 
 Thank you for the response, Jörg.
 
 That is what I have done, copy the interesting bits from the commons
 and Apache parents into our internal parent.  We're not extending from
 either.
 
 I'm not seeing how the commons parent with its release profiles can
 work for pom packaging projects (such as the parent project or
 multimodule projects).  When commons-parent is released, are none of
 the release profiles enabled (rc, release, apache-release)?
>>> 
>>> - rc: the one we use
>> 
>> That was the one we used for creating RCs prior to Nexus.
>> 
>>> - release: automatically activated by M2 (IIRC)
>> 
>> This is the one I normally use.
>> 
>> I think rc and release are fairly similar.
>> 
>> However, I'm not sure either can be used for releasing the parent POM.
> 
> I checked the newer documentation referenced in this thread
> 
> http://wiki.apache.org/commons/UsingNexus
> http://www.apache.org/dev/publishing-maven-artifacts.html
> 
> and found this:
> 
> For Commons Parent, you can do:
> 
> $ mvn clean gpg:sign deploy -Ptest-deploy
> 
> 
> I didn't see any explicit documentation about the actual release of
> Parent to the Nexus staging directory, so I assume it is just
> 
> $ mvn gpg:sign deploy
> 
> ?
> 
> 
>>> - apache-release: outdated?
>> 
>> This is the one in the ASF pom; IIRC it clashes with our requirements.
>> 
 Are any
 of the commons projects currently multimodule builds?
>>> 
>>> http://wiki.apache.org/commons/CreatingReleases
>>> 
>>> vfs is a multi-project
> 
> If I run
> 
> $ mvn clean deploy -Prelease -Ptest-deploy
> 
> on a fresh checkout of commons-vfs2-project it fails with
> 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Commons VFS ... FAILURE [1:20.632s]
> [INFO] Commons VFS Core .. SKIPPED
> [INFO] Commons VFS Examples .. SKIPPED
> [INFO] Commons VFS Distribution .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1:23.425s
> [INFO] Finished at: Wed Apr 25 11:48:18 CDT 2012
> [INFO] Final Memory: 15M/81M
> [INFO] 
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
> on project commons-vfs2-project: Error reading assemblies: No assembly
> descriptors found. -> [Help 1]
> 
>   michael
> 
> -
> 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: [PARENT] release of pom packaging project fails jar plugin

[Michael Heuer]

On Wed, Apr 25, 2012 at 11:57 AM, sebb  wrote:
> On 25 April 2012 17:54, Michael Heuer  wrote:
>> On Wed, Apr 25, 2012 at 4:03 AM, sebb  wrote:
>>> On 25 April 2012 07:48, Jörg Schaible  wrote:
 Michael Heuer wrote:

> Jörg Schaible wrote:
>> Michael Heuer wrote:
>>
>>> I'm forwarding this message originally sent to users@maven that
>>> received no response.  Perhaps dev@commons is more appropriate.
>>
>> why do you think, that extending from Apache Commons parent is a good
>> thing? This parent is crafted so that it fits exactly our (Apache
>> Commons) needs. It is considered internal and is not designed to work for
>> all cases (especially outside its environment).
>>
>> Said that, if you provide patches for this POM that have no side-effects
>> for all our components, we might consider to apply them, but don't expect
>> that someone is maintaining/developing this parent POM like any other
>> Commons component.
>>
>> IMHO, you're better off if you copy the interesting parts into a shared
>> parent of your own.
>
> Thank you for the response, Jörg.
>
> That is what I have done, copy the interesting bits from the commons
> and Apache parents into our internal parent.  We're not extending from
> either.
>
> I'm not seeing how the commons parent with its release profiles can
> work for pom packaging projects (such as the parent project or
> multimodule projects).  When commons-parent is released, are none of
> the release profiles enabled (rc, release, apache-release)?

 - rc: the one we use
>>>
>>> That was the one we used for creating RCs prior to Nexus.
>>>
 - release: automatically activated by M2 (IIRC)
>>>
>>> This is the one I normally use.
>>>
>>> I think rc and release are fairly similar.
>>>
>>> However, I'm not sure either can be used for releasing the parent POM.
>>
>> I checked the newer documentation referenced in this thread
>>
>> http://wiki.apache.org/commons/UsingNexus
>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> and found this:
>>
>> For Commons Parent, you can do:
>>
>> $ mvn clean gpg:sign deploy -Ptest-deploy
>>
>>
>> I didn't see any explicit documentation about the actual release of
>> Parent to the Nexus staging directory, so I assume it is just
>>
>> $ mvn gpg:sign deploy
>>
>
> Yes
>
>>
>>
 - apache-release: outdated?
>>>
>>> This is the one in the ASF pom; IIRC it clashes with our requirements.
>>>
> Are any
> of the commons projects currently multimodule builds?

 http://wiki.apache.org/commons/CreatingReleases

 vfs is a multi-project
>>
>> If I run
>>
>> $ mvn clean deploy -Prelease -Ptest-deploy
>>
>> on a fresh checkout of commons-vfs2-project it fails with
>>
>> [INFO] 
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Commons VFS ... FAILURE 
>> [1:20.632s]
>> [INFO] Commons VFS Core .. SKIPPED
>> [INFO] Commons VFS Examples .. SKIPPED
>> [INFO] Commons VFS Distribution .. SKIPPED
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 1:23.425s
>> [INFO] Finished at: Wed Apr 25 11:48:18 CDT 2012
>> [INFO] Final Memory: 15M/81M
>> [INFO] 
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
>> on project commons-vfs2-project: Error reading assemblies: No assembly
>> descriptors found. -> [Help 1]
>
> As the error message says - there are no assembly descriptors for the
> parent POM.

Right, if I provide an assembly descriptor on the command line, the
local deploy works fine.

I found this in commons-vfs2-project/pom.xml, which addresses the
original problem I reported (jar plugin fails due to missing osgi
manifest for pom packaging project)

  
org.apache.maven.plugins
maven-antrun-plugin

  
vfs-jar-manifest
generate-sources

  run


  


  

  

   michael

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

Re: [Math] maven: Problem with "clirr"

[Dennis Lundberg]

On 2012-04-25 14:36, Gilles Sadowski wrote:
> Hi.
> 
>
> Clirr now fails the build on error:
> ---CUT---
> [ERROR] Unable to find information in class
> [org.apache.commons.math3.linear.SymmLQ referring back to nested class
> [org.apache.commons.math3.linear.SymmLQ$SymmLQEvent ERROR] Unable to
> [find information in class
> [org.apache.commons.math3.optimization.direct.PowellOptimizer referring
> [back to nested class
>
>> [org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
> ---CUT---
>
> Since I don't know what causes those errors, I'd like to be able to
> skip the "clirr" check altogether.

 Clirr does not like the output from the Eclipse compiler.
 Make sure you run mvn clean first - and ensure that Eclipse is not set
 to build the project.

> I tried to mimic settings suggested in an earlier messafe about
> skipping lengthy report, i.e.
> true

 AFAIK, that's not the same as setting a command-line property.
>>>
>>> This syntax worked for other reports (you suggested it).
>>>

> It didn't work.
>
> I tried this:
> false
> as documented here:
> http://clirr.sourceforge.net/clirr-maven/properties.html

 That is for an obsolete version of the Clirr plugin

 The current version is documented at:

 http://mojo.codehaus.org/clirr-maven-plugin/
>>>
>>> The usage page there is rather terse, there is no information about
>>> which properties could alter the behaviour of the plugin (like disabling
>>> it, making just a warning, not a error that fails the build).
>>
>> The properties from command line should be the ones used in "Expression:" 
>> http://mojo.codehaus.org/clirr-maven-plugin/check-mojo.html
> 
> Thanks.
> I tried "failOnError" set to "false". Didn't work.
> 
> Here the stack trace from maven output:
> ---CUT---
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project commons-math3: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project commons-math3: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site 
> failed: 780
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 780
> at 
> org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:666)
> at 
> org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:679)
> at 
> org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.j

[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)

[Continuum@vmbuild]

Online report : 
http://vmbuild.apache.org/continuum/buildResult.action?buildId=21512&projectId=73

Build statistics:
  State: Failed
  Previous State: Failed
  Started at: Wed 25 Apr 2012 20:26:28 +
  Finished at: Wed 25 Apr 2012 20:27:33 +
  Total time: 1m 5s
  Build Trigger: Schedule
  Build Number: 108
  Exit code: 1
  Building machine hostname: vmbuild
  Operating system : Linux(unknown)
  Java Home version : 
  java version "1.6.0_30"
  Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
  Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)

  Builder version :
  Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+)
  Java version: 1.6.0_30
  Java home: /usr/lib/jvm/jdk1.6.0_30/jre
  Default locale: en_US, platform encoding: ANSI_X3.4-1968
  OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: 
"unix"


SCM Changes:

No files changed


Dependencies Changes:

org.apache.commons:commons-pool2:2.0-SNAPSHOT



Build Definition:

POM filename: pom.xml
Goals: clean deploy   
Arguments: --batch-mode
Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: COMMONS_SCHEDULE
Profile Name: Maven 2.2.1
Description: Default Maven 2 Build Definition (Java 1.6)


Test Summary:

Tests: 443
Failures: 1
Errors: 0
Success Rate: 99
Total time: 46.503998


Test Failures:


TestBasicDataSourceFactory
testProperties :
  junit.framework.AssertionFailedError
  junit.framework.AssertionFailedError: expected:<500> but was:<-1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:130)
at junit.framework.Assert.assertEquals(Assert.java:136)
at 
org.apache.commons.dbcp2.TestBasicDataSourceFactory.testProperties(TestBasicDataSourceFactory.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at $Proxy0.invoke(Unknown Source)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)


  



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

[sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?

[Gary Lucas]

I'm taking a stab at transitioning from Sanselan to the new Apache Imaging.   
One thing I've noticed is that one of the EXIF tags my existing software uses 
seems to have been removed from imaging:
 
  public static final TagInfo EXIF_TAG_MODIFY_DATE = new TagInfo(
"Modify Date", 0x0132, FIELD_TYPE_ASCII, 1, EXIF_DIRECTORY_IFD0);
 
 
I'm not familiar with the details behind this tag.   Was it removed because it 
is obsolete or non-standard?An oversight?
 
Thanks.
 
Gary
 
 
 
 
 
Computer Programming is the Art of the Possible
Gary W. Lucas
Sonalysts, Inc.
215 Parkway North
Waterford, CT 06385
(860) 326-3682
41-22-12.35 N / 72-10-07.54 W  (USNG/MGRS:  18T YL 36787 83711)
 

Re: [NET][VFS] Help with FTPS hanging tests

[sebb]

On 25 April 2012 20:55, Gary Gregory  wrote:
> We previously had no FTPS tests. So I added
> org.apache.commons.vfs2.provider.ftps.test.FtpsProviderTestCase_Disabled
> which does the same thing for FTPS that we do for FTP with the addition of
> the SSL sauce on top.
>
> The issue is that all of the test methods that attempt to read from two
> input streams at the same time hang. When the second stream is asked by a
> call site, the code tries to open another connection to the server and it
> hangs forever.
>
> These tests work fine with FTP.
>
> Both FTP and FTPS tests use an embedded Apache FTP Server (MINA).
>
> Is this a bug in code or in the test? In Commons Net, Apache FTP Server
> (MINA), VFS, the test case?
>
> Help please!

Need to try and isolate the different parts.
Can you test with Net independently of VFS?

> Thank you,
> Gary
>
> --
> 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: [NET][VFS] Help with FTPS hanging tests

[Gary Gregory]

On Apr 25, 2012, at 18:26, sebb  wrote:

> On 25 April 2012 20:55, Gary Gregory  wrote:
>> We previously had no FTPS tests. So I added
>> org.apache.commons.vfs2.provider.ftps.test.FtpsProviderTestCase_Disabled
>> which does the same thing for FTPS that we do for FTP with the addition of
>> the SSL sauce on top.
>>
>> The issue is that all of the test methods that attempt to read from two
>> input streams at the same time hang. When the second stream is asked by a
>> call site, the code tries to open another connection to the server and it
>> hangs forever.
>>
>> These tests work fine with FTP.
>>
>> Both FTP and FTPS tests use an embedded Apache FTP Server (MINA).
>>
>> Is this a bug in code or in the test? In Commons Net, Apache FTP Server
>> (MINA), VFS, the test case?
>>
>> Help please!
>
> Need to try and isolate the different parts.
> Can you test with Net independently of VFS?

The test MultipleConnectionTest tries to do that but it works.

Gary
>
>> Thank you,
>> Gary
>>
>> --
>> 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
>

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

[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 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-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: 51 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: 1335408021188
[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.annota

[GUMP@vmgump]: Project commons-graph (in module commons-sandbox) failed

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

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


Full details are available at:

http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/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-graph-*[0-9T].jar] identifier set to project 
name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/graph/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/gump_work/build_commons-sandbox_commons-graph.html
Work Name: build_commons-sandbox_commons-graph (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/commons-sandbox/graph/gump_mvn_settings.xml install 
[Working Directory: /srv/gump/public/workspace/commons-sandbox/graph]
M2_HOME: /opt/maven2
-
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[215,61]
 
withConnections(org.apache.commons.graph.builder.GraphConnection)
 in 
org.apache.commons.graph.builder.LinkedConnectionBuilder>
 cannot be applied to (org.apache.commons.graph.builder.GraphConnection)
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[75,43]
 cannot find symbol
symbol  : method 
applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[82,47]
 cannot find symbol
symbol  : method 
applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[103,43]
 cannot find symbol
symbol  : method 
applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[110,47]
 cannot find symbol
symbol  : method 
applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/spanning/DefaultSpanningTreeSourceSelector.java:[109,20]
 whereEdgesHaveWeights(M) in 
org.apache.commons.graph.shortestpath.PathWeightedEdgesBuilder
 cannot be applied to (org.apache.commons.graph.Mapper)
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/connectivity/DefaultConnectivityAlgorithmsSelector.java:[69,64]
 cannot find symbol
symbol  : method 
applyingDepthFirstSearch(org.apache.commons.graph.connectivity.ConnectedComponentHandler)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>
[INFO] 8 errors 
[INFO] -
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure

/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[201,59]
 
withConnections(org.apache.commons.graph.builder.GraphConnection)
 in 
org.apache.commons.graph.builder.LinkedConnectionBuilder>
 cannot be applied to (org.apache.commons.graph.builder.GraphConnection)
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[215,61]
 
withConnections(org.apache.commons.graph.builder.GraphConnection)
 in 
org.apache.commons.graph.builder.LinkedConnectionBuilder>
 cannot be applied t

Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?

[Damjan Jovanovic]

On Wed, Apr 25, 2012 at 10:30 PM, Gary Lucas  wrote:
> I'm taking a stab at transitioning from Sanselan to the new Apache Imaging.   
> One thing I've noticed is that one of the EXIF tags my existing software uses 
> seems to have been removed from imaging:
>
>  public static final TagInfo EXIF_TAG_MODIFY_DATE = new TagInfo(
>            "Modify Date", 0x0132, FIELD_TYPE_ASCII, 1, EXIF_DIRECTORY_IFD0);
>
>
> I'm not familiar with the details behind this tag.   Was it removed because 
> it is obsolete or non-standard?    An oversight?
>
> Thanks.
>
> Gary

One of the recent changes was deduplication of TIFF tags, and grouping
of tags by specification.

Tag 0x0132 is defined in the TIFF6 specification, so it is now under
TiffTagConstants, and known as TIFF_TAG_DATE_TIME.

Also I am considering replacing the EXIF_ prefix with TIFF_ for all tags.

Damjan

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

[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 116 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: 12 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
-
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.factory.util.TestMethodSignature
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.commons.proxy.provider.TestConstantProvider
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec
Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec
Running org.apache.commons.proxy.interceptor.TestInterceptorChain
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.proxy.invoker.TestNullInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
Running org.apache.commons.proxy.exception.TestDelegateProviderException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.invoker.TestChainInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.193 sec
Running org.apache.commons.proxy.exception.TestProxyFactoryException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.provider.TestBeanProvider
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec

Results :

Tests in error: 
  testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker)

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

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

Please refer to 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 11 seconds
[INFO] Finished at: Thu Apr 26 04:12:06 UTC 2012
[INFO] Final Memory: 24M/58M
[INFO] 
-

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

[GUMP@vmgump]: Project commons-id (in module commons-sandbox) 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-id has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 90 runs.
The current state of this project is 'Failed', with reason 'Missing Build 
Outputs'.
For reference only, the following projects are affected by this:
- commons-id :  Commons Identifier Package


Full details are available at:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/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-id-26042012.jar] identifier set to project 
name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/commons-sandbox/id/gump_mvn_settings.xml
 -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/id/pom.xml
 -INFO- Failed with reason missing build outputs
 -ERROR- Missing Output: 
/srv/gump/public/workspace/commons-sandbox/id/target/commons-id-26042012.jar
 -ERROR- See Directory Listing Work for Missing Outputs
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-sandbox/id/target/surefire-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/gump_work/build_commons-sandbox_commons-id.html
Work Name: build_commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Success
Elapsed: 19 secs
Command Line: /opt/maven2/bin/mvn --batch-mode 
-Dmaven.final.name=commons-id-26042012 --settings 
/srv/gump/public/workspace/commons-sandbox/id/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/commons-sandbox/id]
M2_HOME: /opt/maven2
-
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
Running org.apache.commons.id.serial.AlphanumericGeneratorTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec
Running org.apache.commons.id.uuid.state.ReadOnlyResourceStateImplTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Running org.apache.commons.id.uuid.state.InMemoryStateImplTest
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec <<< 
FAILURE!
Running org.apache.commons.id.serial.LongGeneratorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec
Running org.apache.commons.id.random.SessionIdGeneratorTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.518 sec
Running 
org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.478 sec
Running org.apache.commons.id.serial.PrefixedNumericGeneratorTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
Running org.apache.commons.id.uuid.VersionFourGeneratorTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.049 sec
Running org.apache.commons.id.uuid.state.NodeTest
Tests run: 8, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.016 sec <<< 
FAILURE!
Running org.apache.commons.id.uuid.state.ReadWriteFileStateImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
Running org.apache.commons.id.uuid.task.UUIDTaskTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
Running org.apache.commons.id.serial.NumericGeneratorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec

Results :

Failed tests: 
  testLoad(org.apache.commons.id.uuid.state.InMemoryStateImplTest)

Tests in error: 
  testGetUUIDTime(org.apache.commons.id.uuid.state.NodeTest)
  testGetLastTimestamp(org.apache.commons.id.uuid.state.NodeTest)
  testNodebyteArray(org.apache.commons.id.uuid.state.NodeTest)

Tests run: 121, Failures: 1, Errors: 3, Skipped: 0

[ERROR] There are test failures.

Please refer to 
/srv/gump/public/workspace/commons-sandbox/id/target/surefire-reports for the 
individual test results.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: 
/srv/gump/public/workspace/commons-sandbox/id/target/commons-id-1.0-SNAPSHOT.jar
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 18 seconds
[INFO] Finished at: Thu Apr 26 06:34:01 UTC 2012
[INFO] Final Memory: 30M/72M
[INFO] 
-

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

[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 129 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: 20 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.245 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.092 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

[GUMP@vmgump]: Project commons-jelly-tags-jmx (in module commons-jelly) 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-jelly-tags-jmx 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-jelly-tags-jmx :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jmx/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-jelly-tags-jmx-26042012.jar] identifier set 
to project name
 -ERROR- Output with id mx4j-jmx was not found in project mx4j 
 -ERROR- Unhandled Property: maven.jar.mx4j-jmx on: Maven1 on 
Project:commons-jelly-tags-jmx
 -DEBUG- Dependency on mx4j exists, no need to add for property 
maven.jar.mx4j-jmx.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property 
maven.jar.commons-jexl.
 -DEBUG- (Apache Gump generated) Apache Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/target/test-reports
 -WARNING- No directory 
[/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/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-jmx/gump_work/build_commons-jelly_commons-jelly-tags-jmx.html
Work Name: build_commons-jelly_commons-jelly-tags-jmx (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx]
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

You are working offline so the build will continue, but 
commons-jelly-1.1-SNAPSHOT.jar may be out of date!
The build cannot continue because of the following unsatisfied dependency:

mx4j-jmx-1.1.1.jar; path override doesn't exist: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/*Unset*

Total time: 2 seconds
Finished at: Thu Apr 26 06:44:55 UTC 2012

-

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

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

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

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