Gump | 21 May 09:42
Picon
Favicon

[GUMP <at> vmgump]: Project commons-jelly-tags-jmx (in module commons-jelly) failed

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 general <at> 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 53 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-21052012.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
(Continue reading)

Gump | 21 May 09:33
Picon
Favicon

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

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 general <at> gump.apache.org.

Project commons-scxml-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 177 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: 19 secs
(Continue reading)

Gump | 21 May 09:32
Picon
Favicon

[GUMP <at> vmgump]: Project commons-id (in module commons-sandbox) failed

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 general <at> gump.apache.org.

Project commons-id has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 138 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-21052012.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-21052012.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
(Continue reading)

Gump | 21 May 07:58
Picon
Favicon

[GUMP <at> vmgump]: Project commons-vfs2-sandbox (in module apache-commons) failed

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 general <at> gump.apache.org.

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

Full details are available at:
    http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2-sandbox/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-vfs2-sandbox-21052012.jar] identifier set to project name
 -INFO- Made directory [/srv/gump/public/workspace/apache-commons/vfs/sandbox/target/classes]
 -INFO- Made directory [/srv/gump/public/workspace/apache-commons/vfs/sandbow/target/test-classes]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository

The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2-sandbox/gump_work/build_apache-commons_commons-vfs2-sandbox.html
Work Name: build_apache-commons_commons-vfs2-sandbox (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
(Continue reading)

Continuum@vmbuild | 21 May 07:20
Picon
Favicon

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

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

Build statistics:
  State: Failed
  Previous State: Ok
  Started at: Mon 21 May 2012 05:20:16 +0000
  Finished at: Mon 21 May 2012 05:20:38 +0000
  Total time: 21s
  Build Trigger: Schedule
  Build Number: 189
  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+0000)
          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: bodewig @ Mon 21 May 2012 04:24:20 +0000
Comment: some comments still mention old Ant class name
(Continue reading)

Gump | 21 May 06:37
Picon
Favicon

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

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 general <at> gump.apache.org.

Project commons-proxy-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 164 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: 11 secs
(Continue reading)

Picon
Favicon

[GUMP <at> vmgump]: Project commons-graph (in module commons-sandbox) failed

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 general <at> gump.apache.org.

Project commons-graph 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-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: 15 secs
(Continue reading)

Gump | 21 May 05:01
Picon
Favicon

[GUMP <at> vmgump]: Project commons-betwixt (in module apache-commons) failed

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 general <at> gump.apache.org.

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

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -DEBUG- Sole jar output [commons-betwixt-21052012.jar] identifier set to project name
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/betwixt/target/test-reports
 -DEBUG- Extracted fallback artifacts from Gump Repository

The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-betwixt/gump_work/build_apache-commons_commons-betwixt.html
Work Name: build_apache-commons_commons-betwixt (Type: Build)
Work ended in a state of : Failed
(Continue reading)

Gump | 21 May 04:18
Picon
Favicon

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

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 general <at> gump.apache.org.

Project commons-exec-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - commons-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
(Continue reading)

Thomas Neidhart | 21 May 00:17
Picon

[math] numerical stability problems of continued fraction

Hi,

I have worked on the numerical stability problems (see MATH-718,
MATH-785) of our continued fraction implementation, which is used in
several other classes (Beta, Gamma).

As I was not really convinced with the scaling approach to overcome
overflow and underflow situations which occur quite often, I tried out
the modified Lentz-Thompson algorithm (as outlined in Numerical Recipes,
but I found also other web references).

This seems to solve all the described problems, but the question remains
if this can be included without problems into CM. The algorithm
description in NR is not in source code but on an higher level.

Thomas
Gump | 20 May 09:28
Picon
Favicon

[GUMP <at> vmgump]: Project commons-jelly-tags-jmx (in module commons-jelly) failed

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 general <at> 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 51 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-20052012.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
(Continue reading)


Gmane