[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 68 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: 22 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.206 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.056 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-vfs2 (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-vfs2 has an issue affecting its community integration.
This issue affects 5 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-configuration :  Apache Commons
- commons-configuration-test :  Apache Commons
- commons-vfs2 :  Apache Commons
- commons-vfs2-sandbox :  Apache Commons
- commons-vfs2-test :  Apache Commons


Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2/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-*[0-9T].jar] identifier set to project 
name
 -INFO- Optional dependency org.jdom prerequisite failed with reason build 
failed
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/vfs/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-vfs2/gump_work/build_apache-commons_commons-vfs2.html
Work Name: build_apache-commons_commons-vfs2 (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: /opt/maven3/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/vfs]
M2_HOME: /opt/maven3
-
[INFO] Commons VFS
[INFO] Commons VFS Core
[INFO] Commons VFS Examples
[INFO] Commons VFS Distribution
[INFO] 
[INFO] 
[INFO] Building Commons VFS 2.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (javadoc.resources) @ 
commons-vfs2-project ---
[INFO] Executing tasks

main:
 [copy] Copying 2 files to 
/srv/gump/public/workspace/apache-commons/vfs/target/apidocs/META-INF
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (vfs-jar-manifest) @ 
commons-vfs2-project ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
/srv/gump/public/workspace/apache-commons/vfs/target/osgi
[touch] Creating 
/srv/gump/public/workspace/apache-commons/vfs/target/osgi/MANIFEST.MF
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
commons-vfs2-project ---
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.1:create (default) @ commons-vfs2-project 
---
Downloading: 
http://localhost:8192/maven2/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.7/maven-scm-provider-cvs-commons-1.7.pom
Downloading: 
http://maven.tmatesoft.com/content/repositories/releases/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.7/maven-scm-provider-cvs-commons-1.7.pom
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Commons VFS ... FAILURE [8.619s]
[INFO] Commons VFS Core .. SKIPPED
[INFO] Commons VFS Examples .. SKIPPED
[INFO] Commons VFS Distribution .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 9.882s
[INFO] Finished at: Sun Sep 09 04:48:56 UTC 2012
[INFO] Final Memory: 10M/27M
[INFO] 
[ERROR] Failed to execute goal 
org.codehaus.mojo:buildnumber-maven-plugin:1.1:create (default) on project 
commons-vfs2-project: Execution default of goal 
org.codehaus.mojo:buildnumber-maven-plugin:1.1:create failed: Plugin 
org.codehaus.mojo:buildnumber-maven-plugin:1.1 or one of its dependencies could 
not be resolved: Failed to collect dependencies for 
org.codehaus.mojo:buildnumber-maven-plugin:jar:1.1 (): Failed to read artifact 
descriptor for org.apache.maven.scm:maven-scm-provider-cvs-commons:jar:1.7: 
Could not transfer artifact 
org.apache.maven.scm:maven-scm-provider-cvs-commons:pom:1.7 from/to 
gump-central (http://localhost:8192/maven2): Error transferring file: Invalid 
Http response -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run 

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

[Gump]

To whom it may engage...

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

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


Full details are available at:

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

That said, some information snippets are provided here.

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



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

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

[INFO] ---

[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 68 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: 14 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.006 sec
Running org.apache.commons.proxy.factory.util.TestMethodSignature
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.provider.TestConstantProvider
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 sec
Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec
Running org.apache.commons.proxy.interceptor.TestInterceptorChain
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running org.apache.commons.proxy.invoker.TestNullInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 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.004 sec
Running org.apache.commons.proxy.invoker.TestChainInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec
Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.304 sec
Running org.apache.commons.proxy.exception.TestProxyFactoryException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 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.033 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: 13 seconds
[INFO] Finished at: Sun Sep 09 04:28:07 UTC 2012
[INFO] Final Memory: 25M/60M
[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.o

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

[Gump]

To whom it may engage...

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

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


Full details are available at:

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

That said, some information snippets are provided here.

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



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

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

  Try downloading the file manually from the project website.

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

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

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

--
1 required artifact is missing.

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

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



[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 54 seconds
[INFO] Finished at: Sun Sep 09 04:16:22 UTC 2012
[INFO] Final Memory: 113M/241M
[INFO] 
-

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

[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 2 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
 -INFO- Optional dependency velocity-engine prerequisite failed with reason 
build failed
 -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: 2 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
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
org.apache.commons:commons-graph:jar:0.1-SNAPSHOT for project 
org.apache.commons:commons-graph:jar:0.1-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact from any repository
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:404)
at 
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 68 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
 -INFO- Optional dependency velocity-engine prerequisite failed with reason 
build failed
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/apache-commons/digester/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 1 sec
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: 1347161292719
[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.G

[GUMP@vmgump]: Project commons-imaging (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-imaging has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-imaging :  Commons Imaging
- commons-imaging-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-imaging/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-imaging-*[0-9T].jar] identifier set to 
project name
 -INFO- Optional dependency commons-io failed with reason build failed
 -INFO- Optional dependency velocity-engine prerequisite failed with reason 
build failed
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/imaging/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/imaging/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-imaging/gump_work/build_apache-commons_commons-imaging.html
Work Name: build_apache-commons_commons-imaging (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/imaging/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/imaging]
M2_HOME: /opt/maven2
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
org.apache.commons:commons-imaging:jar:1.0-SNAPSHOT for project 
org.apache.commons:commons-imaging:jar:1.0-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact

[GUMP@vmgump]: Project commons-functor (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-functor has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-functor :  Functor: Function Objects


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-functor/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-functor-1.0-SNAPSHOT.jar] identifier set to 
project name
 -INFO- Optional dependency velocity-engine prerequisite failed with reason 
build failed
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/functor/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/functor/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/functor/target/surefire-reports
 -WARNING- No directory 
[/srv/gump/public/workspace/apache-commons/functor/target/surefire-reports]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-functor/gump_work/build_apache-commons_commons-functor.html
Work Name: build_apache-commons_commons-functor (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/functor/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/functor]
M2_HOME: /opt/maven2
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
null:commons-functor:jar:1.0-SNAPSHOT for project 
null:commons-functor:jar:1.0-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.Resou

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


Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-cli/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-cli-*[0-9T].jar] identifier set to project 
name
 -INFO- Optional dependency velocity-engine prerequisite failed with reason 
build failed
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/cli/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/cli/pom.xml
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-cli/gump_work/build_apache-commons_commons-cli.html
Work Name: build_apache-commons_commons-cli (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/cli/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/cli]
M2_HOME: /opt/maven2
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
commons-cli:commons-cli:jar:1.3-SNAPSHOT for project 
commons-cli:commons-cli:jar:1.3-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact from any repository
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:404)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.res

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

[Gump]

To whom it may engage...

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

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


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

That said, some information snippets are provided here.

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



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

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

[Gump]

To whom it may engage...

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

Project commons-dbcp has an issue affecting its community integration.
This issue affects 12 projects,
 and has been outstanding for 63 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-dbcp :  Object Pooling
- jakarta-tomcat-dbcp :  Servlet 2.4 and JSP 2.0 Reference Implementation
- javax.el :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation (for 
...
- javax.servlet :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation 
(for ...
- javax.servlet.jsp :  Java Servlet 2.5 & Server Pages JSP 2.1 
implementation (for ...
- tomcat-tc6 :  Java Servlet 2.5 & Server Pages JSP 2.1 implementation (for 
...
- tomcat-tc7.0.x :  Tomcat 7.x, a web server implementing Java Servlet 3.0,
...
- tomcat-tc7.0.x-dbcp :  Tomcat 7.x, a web server implementing Java Servlet 
3.0,
...
- tomcat-tc7.0.x-test :  Tomcat 7.x, a web server implementing Java Servlet 
3.0,
...
- tomcat-trunk :  Tomcat 8.x, a web server implementing Java Servlet 3.1,
...
- tomcat-trunk-dbcp :  Tomcat 8.x, a web server implementing Java Servlet 
3.1,
...
- tomcat-trunk-test :  Tomcat 8.x, a web server implementing Java Servlet 
3.1,
...


Full details are available at:

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

That said, some information snippets are provided here.

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



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

[GUMP@vmgump]: Project bcel (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 bcel has an issue affecting its community integration.
This issue affects 96 projects,
 and has been outstanding for 802 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- anakia :  Essentially an XML transformation tool, Anakia uses JDOM and...
- ant-contrib :  Useful little Ant tasks
- ant-contrib-test :  Useful little Ant tasks
- ant-embed-optional :  Historical Embed Proposal for Ant
- bcel :  Byte Code Engineering Library
- bsh-cvs
- commons-id :  Commons Identifier Package
- commons-jelly :  Commons Jelly
- commons-jelly-tags-ant :  Commons Jelly
- commons-jelly-tags-ant-test :  Commons Jelly
- commons-jelly-tags-antlr :  Commons Jelly
- commons-jelly-tags-avalon :  Commons Jelly
- commons-jelly-tags-bean :  Commons Jelly
- commons-jelly-tags-beanshell :  Commons Jelly
- commons-jelly-tags-betwixt :  Commons Jelly
- commons-jelly-tags-bsf :  Commons Jelly
- commons-jelly-tags-define :  Commons Jelly
- commons-jelly-tags-define-test :  Commons Jelly
- commons-jelly-tags-dynabean :  Commons Jelly
- commons-jelly-tags-email :  Commons Jelly
- commons-jelly-tags-fmt :  Commons Jelly
- commons-jelly-tags-fmt-test :  Commons Jelly
- commons-jelly-tags-html :  Commons Jelly
- commons-jelly-tags-http :  Commons Jelly
- commons-jelly-tags-interaction :  Commons Jelly
- commons-jelly-tags-jface :  Commons Jelly
- commons-jelly-tags-jms :  Commons Jelly
- commons-jelly-tags-jmx :  Commons Jelly
- commons-jelly-tags-jsl :  Commons Jelly
- commons-jelly-tags-jsl-test :  Commons Jelly
- commons-jelly-tags-junit :  Commons Jelly
- commons-jelly-tags-log :  Commons Jelly
- commons-jelly-tags-memory :  Commons Jelly
- commons-jelly-tags-regexp :  Commons Jelly
- commons-jelly-tags-soap :  Commons Jelly
- commons-jelly-tags-sql :  Commons Jelly
- commons-jelly-tags-swing :  Commons Jelly
- commons-jelly-tags-swt :  Commons Jelly
- commons-jelly-tags-threads :  Commons Jelly
- commons-jelly-tags-util :  Commons Jelly
- commons-jelly-tags-velocity :  Commons Jelly
- commons-jelly-tags-xml :  Commons Jelly
- commons-jelly-tags-xmlunit :  Commons Jelly
- commons-jelly-test :  Commons Jelly
- db-ddlutils :  Easy-to-use component for working with Database Definition 
(...
- dist-xalan2 :  Release 2.x of the Xalan-Java XSLT processor
- dist-xerces1 :  Java XML Parser
- dom4j :  The flexible XML framework for Java
- dom4j-tests :  The flexible XML framework for Java
- forrest-core :  Apache Forrest software is a publishing framework that 
trans...
- forrest-test :  Apache Forrest software is a publishing framework that 
trans...
- forrest-test-basic :  Apache Forrest software is a publishing framework 
that trans...
- fulcrum-dvsl :  Services Framework
- hamcrest-java-unit-test :  Provides a library of matcher objects (also 
known as constra...
- htmlparser :  HTML Parser
- htmlparser-test :  HTML Parser
- invicta :  Open-source build management tool.
- ivy-tests :  Apache Ivy is a tool for managing (recording, tracking, 
reso...
- jakarta-site2 :  The Jakarta site
- jaxen :  Universal Java XPath Engine
- jaxen-test :  Universal Java XPath Engine
- jdom :  Java XML API
- jgroups :  A Reliable Multicast Communication Toolkit for Java
- jmock2 :  jMock is a library for testing Java code using mock objects.
- jmock2-test :  jMock is a library for testing Java code using mock 
objects.
- junit-addons :  Various JUnit addons and helper classes.
- logging-log4cxx-ant :  Apache log4cxx
- logging-log4cxx-ant-no_wchar_t :  Apache log4cxx
- logging-log4cxx-ant-static :  Apache log4cxx
- lucene-java-contrib :  Java Based Search Engine
- lucene-java-contrib-test :  Java Based Search Engine
- mockito :  Mockito is a mocking framework
- net.sf.xmlunit :  JUnit extension for XML unit tests.
- org.apache.poi :  POI
- org.apache.velocity.velocity-engine :  Velocity Templating engine
- org.apache.xmlgraphics.batik :  Scalable Vector Graphics
- org.jdom :  Java XML API
- poi :  POI
- poi-test :  POI
- tomcat-tc7.0.x-validate :  Tomcat 7.x, a web server implementing Java 
Servlet 3.0,
...
- tomcat-trunk-validate :  Tomcat 8.x, a web server implementing Java 
Servlet 3.1,
...
- velocity-engine :  Velocity Templating engine
- velocity-engine-test :  Velocity Templating engine
- ws-axis-test :  Apache eXtensible Interaction System
- wss4j :  WS-FX Project
- wss4j-test :  WS-FX Project
  

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

[Gump]

To whom it may engage...

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

Project commons-io has an issue affecting its community integration.
This issue affects 23 projects,
 and has been outstanding for 644 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-fileupload :  Commons File Upload Package
- commons-io :  Commons I/O Utility Package
- commons-io-test :  Apache Commons
- forrest-rat :  Apache Forrest software is a publishing framework that 
trans...
- fulcrum-naming :  Services Framework
- fulcrum-osworkflow :  Services Framework
- jakarta-tomcat-4.0 :  Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-catalina :  Servlet 2.4 Reference Implementation
- jakarta-tomcat-coyote-tomcat4 :  Connectors to various web servers
- jakarta-tomcat-jk :  Connectors to various web servers
- jmeter-svn :  Pure Java load testing and performance measurement tool.
   ...
- jmeter-test :  Pure Java load testing and performance measurement tool.
   ...
- org.apache.commons.commons-io :  Apache Commons
- org.apache.xmlgraphics.fop :  XSL-FO (Formatting Objects) processor
- portals-pluto-portal-1.0 :  JSR168 Container
- rat-tasks-antunit-tests :  Release Audit Tool
- solr :  Java Based Search Engine
- solr-test :  Java Based Search Engine
- tomcat-catalina :  Servlet 2.3 and JSP 1.2 Reference Implementation
- xml-fop :  XSL-FO (Formatting Objects) processor
- xml-fop-test :  XSL-FO (Formatting Objects) processor
- xmlgraphics-commons :  Apache XML Graphics Commons - Common Components 
for Batik an...
- xmlgraphics-commons-test :  Apache XML Graphics Commons - Common 
Components for Batik an...


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



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-io/gump_work/build_apache-commons_commons-io.html
Work Name: build_apache-commons_commons-io (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 30 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/io]
M2_HOME: /opt/maven2
-
Downloading: 
http://maven.tmatesoft.com/content/repositories/releases/org/apache/maven/scm/maven-scm-provider-perforce/1.7/maven-scm-provider-perforce-1.7.pom
[INFO] Unable to find resource 
'org.apache.maven.scm:maven-scm-provider-perforce:pom:1.7' in repository 
maven.tmatesoft.com.releases 
(http://maven.tmatesoft.com/content/repositories/releases)
Downloading: 
http://localhost:8192/maven2/org/apache/maven/scm/maven-scm-provider-perforce/1.7/maven-scm-provider-perforce-1.7.pom
2K downloaded  (maven-scm-provider-perforce-1.7.pom)
Downloading: 
http://maven.tmatesoft.com/content/repositories/releases/org/apache/maven/scm/maven-scm-provider-hg/1.7/maven-scm-provider-hg-1.7.pom
[INFO] Unable to find resource 
'org.apache.maven.scm:maven-scm-provider-hg:pom:1.7' in repository 
maven.tmatesoft.com.releases 
(http://maven.tmatesoft.com/content/repositories/releases)
Downloading: 
http://localhost:8192/maven2/org/apache/maven/scm/maven-scm-provider-hg/1.7/maven-scm-provider-hg-1.7.pom
2K downloaded  (maven-scm-provider-hg-1.7.pom)
Downloading: 
http://maven.tmatesoft.com/content/repositories/releases/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/1.13/maven-scm-provider-svnjava-1.13.pom
[INFO] Unable to find resource 
'com.google.code.maven-scm-provider-svnjava:maven-scm-provider-svnjava:pom:1.13'
 in repository maven.tmatesoft.com.releases 
(http://maven.tmatesoft.com/content/repositories/releases)
Downloading: 
http://localhost:8192/maven2/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/1.13/maven-scm-provider-svnjava-1.13.pom
9K downloaded  (maven-scm-provider-svnjava-1.13.pom)
Downloading: 
http://maven.tmatesoft.com/content/repositories/releases/org/sonatype/oss/oss-parent/5/oss-parent-5.pom
[INFO] Unable to find resource 'org.sonatype.oss:oss-parent:pom:5' in 
repository 

Re: [math] workaround to get site reports to run WAS: Re: [math] spinning BOBYQAOptimizerTest

[Thomas Neidhart]

On 09/08/2012 10:21 PM, Thomas Neidhart wrote:
> On 09/08/2012 07:05 PM, Phil Steitz wrote:
>> Per the thread below, "mvn site" now takes an very, very long time
>> to run on many (most?) platforms, so as a workaround until we figure
>> out how to fix the tests or plugins, here is a quick way to get the
>> basic site generated locally with static analysis reports.  Use "mvn
>> clean test" first to verify that tests are all good and then skip
>> the tests when generating the site:
>>
>> mvn -DskipTests=true site
> 
> another way as highlighted by sebb a few weeks ago is to run it like this:
> 
> mvn -Pfast clean site

oh, this is not by default in the pom.xml, you have to add the following
to it (I kept findbugs and pmd enabled):


   
 fast
 
   true
   true
   true
   true


 
  


Thomas

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

Re: [math] workaround to get site reports to run WAS: Re: [math] spinning BOBYQAOptimizerTest

[Thomas Neidhart]

On 09/08/2012 07:05 PM, Phil Steitz wrote:
> Per the thread below, "mvn site" now takes an very, very long time
> to run on many (most?) platforms, so as a workaround until we figure
> out how to fix the tests or plugins, here is a quick way to get the
> basic site generated locally with static analysis reports.  Use "mvn
> clean test" first to verify that tests are all good and then skip
> the tests when generating the site:
> 
> mvn -DskipTests=true site

another way as highlighted by sebb a few weeks ago is to run it like this:

mvn -Pfast clean site

Thomas

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

Re: [configuration] Should we remove list splitting for attributes in XMLConfiguration?

[Oliver Heger]

Am 08.09.2012 18:49, schrieb Ralph Goers:

No objection.

I believe this was done because of the way lists are done in property files - a comma 
separated list of values on a single property.  In XML you would just have multiple 
instances of the element, each with its own value.  This is one of the reasons why having 
the "flat" configuration as the base for hierarchical configurations is bad.

Yes, the idea was to be consistent with the way properties 
configurations work. I created 
https://issues.apache.org/jira/browse/CONFIGURATION-505 for handling 
this change.


Oliver


Ralph


On Sep 8, 2012, at 8:11 AM, Oliver Heger wrote:


Currently XMLConfiguration allows setting multiple values for an attribute 
node. (This is possible through the Configuration interface, but of course not 
supported by XML.) When saving the configuration it tries to encode the list as 
a comma-separated string. On reloading, such strings are split again.

The implementation of this feature is pretty complex because points like 
escaping delimiter characters have to be taken into account. I doubt that it 
works in a reliable way in all possible constellations. OTOH, I don't think 
that this functionality provides much value to users.

So, in short, I propose to remove this feature. I would change the 
implementation to check for attributes with multiple values when the 
configuration is to be saved. If such attributes are detected, an exception can 
be thrown.

Any objections?
Oliver

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




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




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

Re: [configuration] Plan for 2.0

[Oliver Heger]

Am 08.09.2012 18:45, schrieb Ralph Goers:

If you are going to break compatibility the package names need to be changed.

I really dislike CombinedConfiguration.  Having the combined nodes point into 
other configuration nodes makes reloading fragile which is why it now copies 
nodes.  This means that a DynamicCombinedConfiguration that has a common 
default node will have as many copies of the default node as there are 
instances of the CombinedConfiguration.  This uses a large amount of memory.  I 
really wish DefaultConfigurationBuilder worked on an AggregateConfiguration, 
but that isn't designed to support XML.


One proposal for dealing with reloading in future (not fully thought out 
yet):


I would like to make builders a more central concept. Rather than 
creating configuration objects using the new operator (which is btw 
currently problematic for file-based configurations because many of 
their constructors call protected methods to be overridden by 
subclasses), instances should be obtained through builders.


Client code would store the builder rather than the configuration 
object. Each time access to the configuration is needed, the builder is 
queried:


Configuration conf = builder.getConfiguration();
// do something with conf

Then reloading can be moved from the configuration to the builder. There 
can be reloading-aware builder implementations which check whether a new 
configuration has to be created. Otherwise, the same object is returned.


This approach has the following advantages:
- Configuration implementations can be simplified, the whole reloading 
logic can be removed. This code is not trivial, a whole bunch of methods 
contain checks whether reloading is required.
- Threading issues related to reloading can no longer occur inside 
configuration objects.
- Error handling can be improved. Currently, if reloading fails, a 
runtime exception is thrown, and the whole Configuration object is corrupt.
- There is better control when a reload can actually happen. As long as 
a client only operates on a Configuration object (without querying the 
builder), it can be sure that the content does not suddenly changes due 
to a reload operation.


The main drawback is that reloading is less transparent for clients. No 
reload will happen if a client keeps a reference to the Configuration 
without querying it from the builder.


Maybe this approach can also help with CombinedConfiguration. Existing 
instances would not be changed by a reload of one of its children. Only 
when querying the builder, a new instance is returned.


Oliver



The bottom line is that we should think about the classes and interfaces that 
are there and create a more rational hierarchy. For example, 
DefaultConfigurationBuilder should be able to create any kind of combination, 
which means it should work with an Interface, not a concrete class.

I still believe HierarchicalConfiguration should be a base Interface, not a 
Class.

The nonsense with attribute splitting and delimiter parsing needs to go away.

Ralph

On Sep 7, 2012, at 12:46 PM, Oliver Heger wrote:


Hi all,

the pom was updated to make 2.0-SNAPSHOT the current development version. This 
means we are free to implement major changes without having to enforce binary 
backwards compatibility.

The question is: What are the goals for version 2.0? I would recommend to 
define a clear focus so that the next release will not take too long. Obviously 
there are already people waiting for a [configuration] version compatible with 
[lang3].

Some points I have in mind are the following ones:
- Switch to [lang3]. This is the main reason for going to version 2.0 because 
this cannot be done in a binary compatible way.
- Improve thread safety and concurrent implementations in general.
- Rework reloading. This is related to the previous point because I think the 
tight coupling of the current reloading implementation is one of the root 
causes making the implementation of thread-safe configurations so hard.
- Have a look at older Jira tickets which have been postponed because they 
would break binary compatibility.

Any other points, wishes, or opinions? We should discuss the points separately 
when it comes to their implementation.

Oliver

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




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




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

[math] workaround to get site reports to run WAS: Re: [math] spinning BOBYQAOptimizerTest

[Phil Steitz]

Per the thread below, "mvn site" now takes an very, very long time
to run on many (most?) platforms, so as a workaround until we figure
out how to fix the tests or plugins, here is a quick way to get the
basic site generated locally with static analysis reports.  Use "mvn
clean test" first to verify that tests are all good and then skip
the tests when generating the site:

mvn -DskipTests=true site

Phil

On 8/7/12 12:21 PM, Phil Steitz wrote:
> On 8/7/12 11:29 AM, Luc Maisonobe
>> Le 07/08/2012 00:21, Phil Steitz a écrit :
>>> On 8/6/12 2:53 PM, Gilles Sadowski wrote:
 On Sun, Aug 05, 2012 at 03:13:33PM -0700, Phil Steitz wrote:
> The site build just hung on me due to
> BOBYQAOptimizerTest.testConstrainedRosenWithMoreInterpolationPoints
> spinning.  A sample thread dump showing the spinning thread is show
> below.  Above the reference to
> BOBYQAOptimizer.doOptimize(BOBYQAOptimizer.java:246), successive
> dumps change.  The code continues to run, but does not complete. 
> The hang happened during the coberta instrumented test run.
>
> at
> org.apache.commons.math3.optimization.direct.BOBYQAOptimizer.bobyqb(BOBYQAOptimizer.java:970)
> at
> org.apache.commons.math3.optimization.direct.BOBYQAOptimizer.bobyqa(BOBYQAOptimizer.java:334)
> at
> org.apache.commons.math3.optimization.direct.BOBYQAOptimizer.doOptimize(BOBYQAOptimizer.java:246)
> at
> org.apache.commons.math3.optimization.direct.BaseAbstractMultivariateOptimizer.optimize(BaseAbstractMultivariateOptimizer.java:126)
> at
> org.apache.commons.math3.optimization.direct.BaseAbstractMultivariateSimpleBoundsOptimizer.optimize(BaseAbstractMultivariateSimpleBoundsOptimizer.java:139)
> at
> org.apache.commons.math3.optimization.direct.BOBYQAOptimizerTest.doTest(BOBYQAOptimizerTest.java:321)
> at
> org.apache.commons.math3.optimization.direct.BOBYQAOptimizerTest.testConstrainedRosenWithMoreInterpolationPoints(BOBYQAOptimizerTest.java:249)
 Runs fine here...
 Excerpt from Cobertura report:
 BOBYQAOptimizer   87%  1022/1162   84% 525/624  23
>>> Interesting.  Hangs every time for me on
>> Same here.
>> I wanted to use cobertura for testing the studff I am working on, and
>> could not succeed.
> What I don't get is why this happens only when running the
> coberta-instrumented code and why it is not actually hung, just not
> terminating.  Successive thread dumps show that processing is
> continuing.  Have we seen other situations where this test does not
> terminate?
>
> Phil
>> I'm running the following versions, on a Linux box with Debian squeeze
>> OS, a three years old AMD 64 processor and about 6 Gbytes RAM.
>>
>> (lehrin) luc% mvn -version
>> Apache Maven 2.2.1 (rdebian-8)
>> Java version: 1.6.0_24
>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>> Default locale: fr_FR, platform encoding: UTF-8
>> OS name: "linux" version: "3.2.0-3-amd64" arch: "amd64" Family: "unix"
>> (lehrin) luc% java -version
>> java version "1.6.0_24"
>> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-2)
>> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>> (lehrin) luc%
>>
>> Luc
>>
>>> BOBYQAOptimizer.doOptimize(BOBYQAOptimizer.java:246)
>>>
>>> running
>>>
>>> Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
>>> java version "1.6.0_33"
>>> Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
>>>
>>> Phil
>>>
 Gilles

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


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


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

Re: [configuration] Should we remove list splitting for attributes in XMLConfiguration?

[Ralph Goers]

No objection.

I believe this was done because of the way lists are done in property files - a 
comma separated list of values on a single property.  In XML you would just 
have multiple instances of the element, each with its own value.  This is one 
of the reasons why having the "flat" configuration as the base for hierarchical 
configurations is bad.

Ralph


On Sep 8, 2012, at 8:11 AM, Oliver Heger wrote:

> Currently XMLConfiguration allows setting multiple values for an attribute 
> node. (This is possible through the Configuration interface, but of course 
> not supported by XML.) When saving the configuration it tries to encode the 
> list as a comma-separated string. On reloading, such strings are split again.
> 
> The implementation of this feature is pretty complex because points like 
> escaping delimiter characters have to be taken into account. I doubt that it 
> works in a reliable way in all possible constellations. OTOH, I don't think 
> that this functionality provides much value to users.
> 
> So, in short, I propose to remove this feature. I would change the 
> implementation to check for attributes with multiple values when the 
> configuration is to be saved. If such attributes are detected, an exception 
> can be thrown.
> 
> Any objections?
> Oliver
> 
> -
> 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: [configuration] Plan for 2.0

[Ralph Goers]

If you are going to break compatibility the package names need to be changed.

I really dislike CombinedConfiguration.  Having the combined nodes point into 
other configuration nodes makes reloading fragile which is why it now copies 
nodes.  This means that a DynamicCombinedConfiguration that has a common 
default node will have as many copies of the default node as there are 
instances of the CombinedConfiguration.  This uses a large amount of memory.  I 
really wish DefaultConfigurationBuilder worked on an AggregateConfiguration, 
but that isn't designed to support XML.

The bottom line is that we should think about the classes and interfaces that 
are there and create a more rational hierarchy. For example, 
DefaultConfigurationBuilder should be able to create any kind of combination, 
which means it should work with an Interface, not a concrete class.

I still believe HierarchicalConfiguration should be a base Interface, not a 
Class.

The nonsense with attribute splitting and delimiter parsing needs to go away.

Ralph

On Sep 7, 2012, at 12:46 PM, Oliver Heger wrote:

> Hi all,
> 
> the pom was updated to make 2.0-SNAPSHOT the current development version. 
> This means we are free to implement major changes without having to enforce 
> binary backwards compatibility.
> 
> The question is: What are the goals for version 2.0? I would recommend to 
> define a clear focus so that the next release will not take too long. 
> Obviously there are already people waiting for a [configuration] version 
> compatible with [lang3].
> 
> Some points I have in mind are the following ones:
> - Switch to [lang3]. This is the main reason for going to version 2.0 because 
> this cannot be done in a binary compatible way.
> - Improve thread safety and concurrent implementations in general.
> - Rework reloading. This is related to the previous point because I think the 
> tight coupling of the current reloading implementation is one of the root 
> causes making the implementation of thread-safe configurations so hard.
> - Have a look at older Jira tickets which have been postponed because they 
> would break binary compatibility.
> 
> Any other points, wishes, or opinions? We should discuss the points 
> separately when it comes to their implementation.
> 
> Oliver
> 
> -
> 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] Logistic, Probit regerssion and Tolerance checks

[Phil Steitz]

On 9/8/12 8:43 AM, marios michaelidis wrote:
> Hi Giles, 
> Per your questions, everything is done, so I just uploaded the class in a txt 
> format. You may run it too and tell me how it performs.
> The only thing I am not certain is in which package it should go. My proposal 
> is to go with correlations as it checks multi-colinearity.
> If I got everything in the format you want and generally everything is right 
> (which I rarely manage with the first try!), I will start uploading other 
> works.
> Regards
> Marios

As noted on the JIRA, I think this should go in regression, as it is
really a regression diagnostic.  At first, I thought about just
adding it to the OLS multiple regression class, but given that it
may be used by multiple regression classes, I agreee it is better to
keep it separate.  Per Gilles' comments below, in order to get this
committed, we need unit tests and clean checkstyle results.   Feel
free to ask here or privately if you need help getting your code
integrated into the [math] build or getting the static analysis
checks to run (checkstyle, findbugs).

Phil
>
>> Date: Sat, 8 Sep 2012 11:59:10 +0200
>> From: gil...@harfang.homelinux.org
>> To: dev@commons.apache.org
>> Subject: Re: [math] Logistic, Probit regerssion and Tolerance checks
>>
>> On Sat, Sep 08, 2012 at 10:50:29AM +0300, marios michaelidis wrote:
>>> Hi everyone,
>>> I will start with the tolerance and Vif checks, because it is smaller and I 
>>> want to get familiar with the system. I have created a relevant ticket 
>>> labelled as "
>>> I would like to include a VIF and TOLERANCE check for a 2 dimensional 
>>> double array, vey commonly used by major packages to determine variables 
>>> that cause multi-colinearity issues and should be excluded from the models"
>>> Shall I just upload the class?
>> If you think that all design issues are clear, and you are ready to adapt
>> your code for inclusion to Commons Math (or have done so already), then yes,
>> you could just attach your proposed code to the issue on the bug-tracking
>> system.
>>
>> If you want to discuss design issues (such as how to best adapt your code),
>> it is better to ask specific questions on this ML.
>>
>>> What else do I need to do?
>> It depends on where you are in the process...
>>
>> Did you already check out the CM source code?
>> Did you include your contribution in your working copy of CM?
>> Does it follow the style used in CM (API and formatting)?
>> Does it compile?
>> Did you write unit tests that cover all functionalities?
>> Do they pass?
>>
>>
>> Best regards,
>> Gilles
>>
>>> Regards
>>> Marios
 From: ted.dunn...@gmail.com
 Date: Fri, 7 Sep 2012 16:09:34 -0700
 Subject: Re: [math] Logistic, Probit regerssion and Tolerance checks
 To: dev@commons.apache.org

 On Fri, Sep 7, 2012 at 4:06 PM, Phil Steitz  wrote:

> On 9/7/12 3:28 PM, Ted Dunning wrote:
>>> Patches welcome!
>>>
>> Would normally love to, but I can't do more than kibitz based on other
>> implementations I have done.
>>
> OK, lets start with what Marios has and see where we can take it.
>
>
 Cool.
>>>   
>> -
>> 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-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.
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: 2 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
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
org.apache.commons:commons-graph:jar:0.1-SNAPSHOT for project 
org.apache.commons:commons-graph:jar:0.1-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact from any repository
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:404)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216)
... 21 more
[INFO] ---

RE: [math] Logistic, Probit regerssion and Tolerance checks

[marios michaelidis]

Hi Giles, 
Per your questions, everything is done, so I just uploaded the class in a txt 
format. You may run it too and tell me how it performs.
The only thing I am not certain is in which package it should go. My proposal 
is to go with correlations as it checks multi-colinearity.
If I got everything in the format you want and generally everything is right 
(which I rarely manage with the first try!), I will start uploading other works.
Regards
Marios

> Date: Sat, 8 Sep 2012 11:59:10 +0200
> From: gil...@harfang.homelinux.org
> To: dev@commons.apache.org
> Subject: Re: [math] Logistic, Probit regerssion and Tolerance checks
> 
> On Sat, Sep 08, 2012 at 10:50:29AM +0300, marios michaelidis wrote:
> > 
> > Hi everyone,
> > I will start with the tolerance and Vif checks, because it is smaller and I 
> > want to get familiar with the system. I have created a relevant ticket 
> > labelled as "
> > I would like to include a VIF and TOLERANCE check for a 2 dimensional 
> > double array, vey commonly used by major packages to determine variables 
> > that cause multi-colinearity issues and should be excluded from the models"
> > Shall I just upload the class?
> 
> If you think that all design issues are clear, and you are ready to adapt
> your code for inclusion to Commons Math (or have done so already), then yes,
> you could just attach your proposed code to the issue on the bug-tracking
> system.
> 
> If you want to discuss design issues (such as how to best adapt your code),
> it is better to ask specific questions on this ML.
> 
> > What else do I need to do?
> 
> It depends on where you are in the process...
> 
> Did you already check out the CM source code?
> Did you include your contribution in your working copy of CM?
> Does it follow the style used in CM (API and formatting)?
> Does it compile?
> Did you write unit tests that cover all functionalities?
> Do they pass?
> 
> 
> Best regards,
> Gilles
> 
> > Regards
> > Marios
> > > From: ted.dunn...@gmail.com
> > > Date: Fri, 7 Sep 2012 16:09:34 -0700
> > > Subject: Re: [math] Logistic, Probit regerssion and Tolerance checks
> > > To: dev@commons.apache.org
> > > 
> > > On Fri, Sep 7, 2012 at 4:06 PM, Phil Steitz  wrote:
> > > 
> > > > On 9/7/12 3:28 PM, Ted Dunning wrote:
> > > > >> Patches welcome!
> > > > >>
> > > > > Would normally love to, but I can't do more than kibitz based on other
> > > > > implementations I have done.
> > > > >
> > > > OK, lets start with what Marios has and see where we can take it.
> > > >
> > > >
> > > Cool.
> >   
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 
  

[configuration] Should we remove list splitting for attributes in XMLConfiguration?

[Oliver Heger]

Currently XMLConfiguration allows setting multiple values for an 
attribute node. (This is possible through the Configuration interface, 
but of course not supported by XML.) When saving the configuration it 
tries to encode the list as a comma-separated string. On reloading, such 
strings are split again.


The implementation of this feature is pretty complex because points like 
escaping delimiter characters have to be taken into account. I doubt 
that it works in a reliable way in all possible constellations. OTOH, I 
don't think that this functionality provides much value to users.


So, in short, I propose to remove this feature. I would change the 
implementation to check for attributes with multiple values when the 
configuration is to be saved. If such attributes are detected, an 
exception can be thrown.


Any objections?
Oliver

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

Re: [configuration] Plan for 2.0

[Oliver Heger]

Am 08.09.2012 03:44, schrieb sebb:

On 7 September 2012 20:46, Oliver Heger  wrote:

Hi all,

the pom was updated to make 2.0-SNAPSHOT the current development version.
This means we are free to implement major changes without having to enforce
binary backwards compatibility.


BC breakage will require package and Maven coordinate changes at some
point just before release.

Yes, I am aware of this.




The question is: What are the goals for version 2.0? I would recommend to
define a clear focus so that the next release will not take too long.
Obviously there are already people waiting for a [configuration] version
compatible with [lang3].

Some points I have in mind are the following ones:
- Switch to [lang3]. This is the main reason for going to version 2.0
because this cannot be done in a binary compatible way.


Not sure I follow that.
Why would changing a dependency affect the API for Configuration?
Does not make sense to me.
Some classes of [lang] are exposed in the public API of [configuration]. 
For instance, variable substitution in configuration files is done by a 
org.apache.commons.lang.text.StrSubstitutor object. The StrSubstitutor 
to use can be set. So switching to [lang3] will effectively change the 
public API of [configuration] in an incompatible way.


Oliver




- Improve thread safety and concurrent implementations in general.
- Rework reloading. This is related to the previous point because I think
the tight coupling of the current reloading implementation is one of the
root causes making the implementation of thread-safe configurations so hard.
- Have a look at older Jira tickets which have been postponed because they
would break binary compatibility.

Any other points, wishes, or opinions? We should discuss the points
separately when it comes to their implementation.

Oliver

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



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




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

[GUMP@vmgump]: Project commons-imaging (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-imaging has an issue affecting its community integration.
This issue affects 2 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-imaging :  Commons Imaging
- commons-imaging-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-imaging/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-imaging-*[0-9T].jar] identifier set to 
project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/imaging/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/imaging/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-imaging/gump_work/build_apache-commons_commons-imaging.html
Work Name: build_apache-commons_commons-imaging (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/imaging/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/imaging]
M2_HOME: /opt/maven2
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
org.apache.commons:commons-imaging:jar:1.0-SNAPSHOT for project 
org.apache.commons:commons-imaging:jar:1.0-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact from any repository
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:404)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver

[GUMP@vmgump]: Project commons-functor (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-functor 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-functor :  Functor: Function Objects


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-functor/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-functor-1.0-SNAPSHOT.jar] identifier set to 
project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/functor/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/functor/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/functor/target/surefire-reports
 -WARNING- No directory 
[/srv/gump/public/workspace/apache-commons/functor/target/surefire-reports]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-functor/gump_work/build_apache-commons_commons-functor.html
Work Name: build_apache-commons_commons-functor (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/functor/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/functor]
M2_HOME: /opt/maven2
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
null:commons-functor:jar:1.0-SNAPSHOT for project 
null:commons-functor:jar:1.0-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'org.apache.commons:commons-parent' not found in repository: Unable to download 
the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)

 for project org.apache.commons:commons-parent
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  org.apache.commons:commons-parent:pom:25

from the specified remote repositories:
  gump-central (http://localhost:8192/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
... 19 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact from any repository
at 
org.apache.maven.artifact.manager.Def

[GUMP@vmgump]: Project commons-cli (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-cli has an issue affecting its community integration.
This issue affects 43 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-cli :  Commons CLI Package
- commons-id :  Commons Identifier Package
- commons-jelly :  Commons Jelly
- commons-jelly-tags-ant :  Commons Jelly
- commons-jelly-tags-ant-test :  Commons Jelly
- commons-jelly-tags-antlr :  Commons Jelly
- commons-jelly-tags-avalon :  Commons Jelly
- commons-jelly-tags-bean :  Commons Jelly
- commons-jelly-tags-beanshell :  Commons Jelly
- commons-jelly-tags-betwixt :  Commons Jelly
- commons-jelly-tags-bsf :  Commons Jelly
- commons-jelly-tags-define :  Commons Jelly
- commons-jelly-tags-define-test :  Commons Jelly
- commons-jelly-tags-dynabean :  Commons Jelly
- commons-jelly-tags-email :  Commons Jelly
- commons-jelly-tags-fmt :  Commons Jelly
- commons-jelly-tags-fmt-test :  Commons Jelly
- commons-jelly-tags-html :  Commons Jelly
- commons-jelly-tags-http :  Commons Jelly
- commons-jelly-tags-interaction :  Commons Jelly
- commons-jelly-tags-jface :  Commons Jelly
- commons-jelly-tags-jms :  Commons Jelly
- commons-jelly-tags-jmx :  Commons Jelly
- commons-jelly-tags-jsl :  Commons Jelly
- commons-jelly-tags-jsl-test :  Commons Jelly
- commons-jelly-tags-junit :  Commons Jelly
- commons-jelly-tags-log :  Commons Jelly
- commons-jelly-tags-memory :  Commons Jelly
- commons-jelly-tags-regexp :  Commons Jelly
- commons-jelly-tags-soap :  Commons Jelly
- commons-jelly-tags-sql :  Commons Jelly
- commons-jelly-tags-swing :  Commons Jelly
- commons-jelly-tags-swt :  Commons Jelly
- commons-jelly-tags-threads :  Commons Jelly
- commons-jelly-tags-util :  Commons Jelly
- commons-jelly-tags-velocity :  Commons Jelly
- commons-jelly-tags-xml :  Commons Jelly
- commons-jelly-tags-xmlunit :  Commons Jelly
- commons-jelly-test :  Commons Jelly
- forrest-rat :  Apache Forrest software is a publishing framework that 
trans...
- lucene-java-contrib :  Java Based Search Engine
- lucene-java-contrib-test :  Java Based Search Engine
- rat-tasks-antunit-tests :  Release Audit Tool


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



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-cli/gump_work/build_apache-commons_commons-cli.html
Work Name: build_apache-commons_commons-cli (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/cli/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/cli]
M2_HOME: /opt/maven2
-
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache.commons:commons-parent for project: 
commons-cli:commons-cli:jar:1.3-SNAPSHOT for project 
commons-cli:commons-cli:jar:1.3-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(D

Re: [math] Logistic, Probit regerssion and Tolerance checks

[Gilles Sadowski]

On Sat, Sep 08, 2012 at 10:50:29AM +0300, marios michaelidis wrote:
> 
> Hi everyone,
> I will start with the tolerance and Vif checks, because it is smaller and I 
> want to get familiar with the system. I have created a relevant ticket 
> labelled as "
> I would like to include a VIF and TOLERANCE check for a 2 dimensional double 
> array, vey commonly used by major packages to determine variables that cause 
> multi-colinearity issues and should be excluded from the models"
> Shall I just upload the class?

If you think that all design issues are clear, and you are ready to adapt
your code for inclusion to Commons Math (or have done so already), then yes,
you could just attach your proposed code to the issue on the bug-tracking
system.

If you want to discuss design issues (such as how to best adapt your code),
it is better to ask specific questions on this ML.

> What else do I need to do?

It depends on where you are in the process...

Did you already check out the CM source code?
Did you include your contribution in your working copy of CM?
Does it follow the style used in CM (API and formatting)?
Does it compile?
Did you write unit tests that cover all functionalities?
Do they pass?


Best regards,
Gilles

> Regards
> Marios
> > From: ted.dunn...@gmail.com
> > Date: Fri, 7 Sep 2012 16:09:34 -0700
> > Subject: Re: [math] Logistic, Probit regerssion and Tolerance checks
> > To: dev@commons.apache.org
> > 
> > On Fri, Sep 7, 2012 at 4:06 PM, Phil Steitz  wrote:
> > 
> > > On 9/7/12 3:28 PM, Ted Dunning wrote:
> > > >> Patches welcome!
> > > >>
> > > > Would normally love to, but I can't do more than kibitz based on other
> > > > implementations I have done.
> > > >
> > > OK, lets start with what Marios has and see where we can take it.
> > >
> > >
> > Cool.
> 

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

RE: [math] Logistic, Probit regerssion and Tolerance checks

[marios michaelidis]

Hi everyone,
I will start with the tolerance and Vif checks, because it is smaller and I 
want to get familiar with the system. I have created a relevant ticket labelled 
as "
I would like to include a VIF and TOLERANCE check for a 2 dimensional double 
array, vey commonly used by major packages to determine variables that cause 
multi-colinearity issues and should be excluded from the models"
Shall I just upload the class?
What else do I need to do?
Regards
Marios
> From: ted.dunn...@gmail.com
> Date: Fri, 7 Sep 2012 16:09:34 -0700
> Subject: Re: [math] Logistic, Probit regerssion and Tolerance checks
> To: dev@commons.apache.org
> 
> On Fri, Sep 7, 2012 at 4:06 PM, Phil Steitz  wrote:
> 
> > On 9/7/12 3:28 PM, Ted Dunning wrote:
> > >> Patches welcome!
> > >>
> > > Would normally love to, but I can't do more than kibitz based on other
> > > implementations I have done.
> > >
> > OK, lets start with what Marios has and see where we can take it.
> >
> >
> Cool.