[GUMP@vmgump]: Project commons-jelly-tags-jmx (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-jelly-tags-jmx has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 7 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jmx : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jmx/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-jelly-tags-jmx-27042012.jar] identifier set to project name -ERROR- Output with id mx4j-jmx was not found in project mx4j -ERROR- Unhandled Property: maven.jar.mx4j-jmx on: Maven1 on Project:commons-jelly-tags-jmx -DEBUG- Dependency on mx4j exists, no need to add for property maven.jar.mx4j-jmx. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property maven.jar.commons-jexl. -DEBUG- (Apache Gump generated) Apache Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/target/test-reports -WARNING- No directory [/srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jmx/gump_work/build_commons-jelly_commons-jelly-tags-jmx.html Work Name: build_commons-jelly_commons-jelly-tags-jmx (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx] - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 You are working offline so the build will continue, but commons-jelly-1.1-SNAPSHOT.jar may be out of date! The build cannot continue because of the following unsatisfied dependency: mx4j-jmx-1.1.1.jar; path override doesn't exist: /srv/gump/public/workspace/commons-jelly/jelly-tags/jmx/*Unset* Total time: 1 seconds Finished at: Fri Apr 27 06:48:43 UTC 2012 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jmx/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jmx/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 1227042012, vmgump.apache.org:vmgump:1227042012 Gump E-mail Identifier (unique within run) #52. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at 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 131 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.167 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.066 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-id (in module commons-sandbox) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-id has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 92 runs.
The current state of this project is 'Failed', with reason 'Missing Build
Outputs'.
For reference only, the following projects are affected by this:
- commons-id : Commons Identifier Package
Full details are available at:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [commons-id-27042012.jar] identifier set to project
name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/commons-sandbox/id/gump_mvn_settings.xml
-DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/id/pom.xml
-INFO- Failed with reason missing build outputs
-ERROR- Missing Output:
/srv/gump/public/workspace/commons-sandbox/id/target/commons-id-27042012.jar
-ERROR- See Directory Listing Work for Missing Outputs
-INFO- Project Reports in:
/srv/gump/public/workspace/commons-sandbox/id/target/surefire-reports
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/gump_work/build_commons-sandbox_commons-id.html
Work Name: build_commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Success
Elapsed: 36 secs
Command Line: /opt/maven2/bin/mvn --batch-mode
-Dmaven.final.name=commons-id-27042012 --settings
/srv/gump/public/workspace/commons-sandbox/id/gump_mvn_settings.xml package
[Working Directory: /srv/gump/public/workspace/commons-sandbox/id]
M2_HOME: /opt/maven2
-
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.id.serial.AlphanumericGeneratorTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec
Running org.apache.commons.id.uuid.state.ReadOnlyResourceStateImplTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.commons.id.uuid.state.InMemoryStateImplTest
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec <<<
FAILURE!
Running org.apache.commons.id.serial.LongGeneratorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.apache.commons.id.random.SessionIdGeneratorTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.637 sec
Running
org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.479 sec
Running org.apache.commons.id.serial.PrefixedNumericGeneratorTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running org.apache.commons.id.uuid.VersionFourGeneratorTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.249 sec
Running org.apache.commons.id.uuid.state.NodeTest
Tests run: 8, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.018 sec <<<
FAILURE!
Running org.apache.commons.id.uuid.state.ReadWriteFileStateImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
Running org.apache.commons.id.uuid.task.UUIDTaskTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Running org.apache.commons.id.serial.NumericGeneratorTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
Results :
Failed tests:
testLoad(org.apache.commons.id.uuid.state.InMemoryStateImplTest)
Tests in error:
testGetUUIDTime(org.apache.commons.id.uuid.state.NodeTest)
testGetLastTimestamp(org.apache.commons.id.uuid.state.NodeTest)
testNodebyteArray(org.apache.commons.id.uuid.state.NodeTest)
Tests run: 121, Failures: 1, Errors: 3, Skipped: 0
[ERROR] There are test failures.
Please refer to
/srv/gump/public/workspace/commons-sandbox/id/target/surefire-reports for the
individual test results.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/srv/gump/public/workspace/commons-sandbox/id/target/commons-id-1.0-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 34 seconds
[INFO] Finished at: Fri Apr 27 06:38:03 UTC 2012
[INFO] Final Memory: 30M/72M
[INFO]
-
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/rss.xml
- Atom: h
[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at 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 118 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-proxy-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html Work Name: build_apache-commons_commons-proxy-test (Type: Build) Work ended in a state of : Failed Elapsed: 12 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/proxy] M2_HOME: /opt/maven2 - Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.factory.util.TestMethodSignature Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.proxy.provider.TestConstantProvider Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec Running org.apache.commons.proxy.interceptor.TestInterceptorChain Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.invoker.TestNullInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running org.apache.commons.proxy.exception.TestDelegateProviderException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running org.apache.commons.proxy.invoker.TestChainInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.198 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.proxy.provider.TestBeanProvider Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Results : Tests in error: testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker) Tests run: 179, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 11 seconds [INFO] Finished at: Fri Apr 27 04:14:44 UTC 2012 [INFO] Final Memory: 24M/58M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml - Atom: http://vmgump.apache.o
[GUMP@vmgump]: Project commons-graph (in module commons-sandbox) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-graph has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 83 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-graph : Apache commons sandbox Full details are available at: http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-graph-*[0-9T].jar] identifier set to project name -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/graph/pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/gump_work/build_commons-sandbox_commons-graph.html Work Name: build_commons-sandbox_commons-graph (Type: Build) Work ended in a state of : Failed Elapsed: 16 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml install [Working Directory: /srv/gump/public/workspace/commons-sandbox/graph] M2_HOME: /opt/maven2 - [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[215,61] withConnections(org.apache.commons.graph.builder.GraphConnection) in org.apache.commons.graph.builder.LinkedConnectionBuilder> cannot be applied to (org.apache.commons.graph.builder.GraphConnection) [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[75,43] cannot find symbol symbol : method applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelector>> [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[82,47] cannot find symbol symbol : method applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelector>> [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[103,43] cannot find symbol symbol : method applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelector>> [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[110,47] cannot find symbol symbol : method applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler,W>) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelector>> [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/spanning/DefaultSpanningTreeSourceSelector.java:[109,20] whereEdgesHaveWeights(M) in org.apache.commons.graph.shortestpath.PathWeightedEdgesBuilder cannot be applied to (org.apache.commons.graph.Mapper) [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/connectivity/DefaultConnectivityAlgorithmsSelector.java:[69,64] cannot find symbol symbol : method applyingDepthFirstSearch(org.apache.commons.graph.connectivity.ConnectedComponentHandler) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelector> [INFO] 8 errors [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[201,59] withConnections(org.apache.commons.graph.builder.GraphConnection) in org.apache.commons.graph.builder.LinkedConnectionBuilder> cannot be applied to (org.apache.commons.graph.builder.GraphConnection) /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[215,61] withConnections(org.apache.commons.graph.builder.GraphConnection) in org.apache.commons.graph.builder.LinkedConnectionBuilder> cannot be applied t
[GUMP@vmgump]: Project commons-digester3 (in module apache-commons) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This issue affects 2 projects,
and has been outstanding for 42 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-digester3 : XML to Java Object Configuration
- commons-digester3-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [commons-digester3-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/digester/pom.xml
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Failed
Elapsed: 49 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/apache-commons/digester]
M2_HOME: /opt/maven2
-
[INFO] [remote-resources:process {execution: default}]
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd
/srv/gump/public/workspace/apache-commons/digester/annotations-processor && svn
--non-interactive info
[INFO] Working directory:
/srv/gump/public/workspace/apache-commons/digester/annotations-processor
[INFO] Storing buildNumber: ?? at timestamp: 1335494584072
[INFO] Executing: /bin/sh -c cd
/srv/gump/public/workspace/apache-commons/digester/annotations-processor && svn
--non-interactive info
[INFO] Working directory:
/srv/gump/public/workspace/apache-commons/digester/annotations-processor
[INFO] Storing buildScmBranch: UNKNOWN_BRANCH
[debug] execute contextualize
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 5 source files to
/srv/gump/public/workspace/apache-commons/digester/annotations-processor/target/classes
[INFO] [bundle:manifest {execution: bundle-manifest}]
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/srv/gump/public/workspace/apache-commons/digester/annotations-processor/src/test/resources
[INFO] Copying 0 resource to META-INF
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 3 source files to
/srv/gump/public/workspace/apache-commons/digester/annotations-processor/target/test-classes
>@org.apache.commons.digester3.annotations.rules.ObjectCreate(pattern="rss/channel")
>@org.apache.commons.digester3.annotations.rules.ObjectCreate(pattern="rss/channel/image")
>@org.apache.commons.digester3.annotations.rules.ObjectCreate(pattern="rss/channel/item")
>
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] error: Impossible to generate class
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule:
Attempt to recreate a file for type
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule
[ERROR] error: Impossible to generate class
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule:
Attempt to recreate a file for type
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule
[INFO] 2 errors
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
error: Impossible to generate class
org.apache.commons.digester3.annotations.processor.GeneratedRulesModule:
Attempt to recreate a file for type
org.apache.commons.digester3.annota
[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=21551&projectId=73 Build statistics: State: Failed Previous State: Failed Started at: Thu 26 Apr 2012 23:32:04 + Finished at: Thu 26 Apr 2012 23:33:09 + Total time: 1m 4s Build Trigger: Forced Build Number: 108 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_30 Java home: /usr/lib/jvm/jdk1.6.0_30/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: Changed: sebb @ Thu 26 Apr 2012 23:31:30 + Comment: GOP no longer throws SQLException Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/BasicDataSource.java ( 1331149 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition (Java 1.6) Test Summary: Tests: 443 Failures: 1 Errors: 0 Success Rate: 99 Total time: 46.876995 Test Failures: TestBasicDataSourceFactory testProperties : junit.framework.AssertionFailedError junit.framework.AssertionFailedError: expected:<500> but was:<-1> at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.failNotEquals(Assert.java:287) at junit.framework.Assert.assertEquals(Assert.java:67) at junit.framework.Assert.assertEquals(Assert.java:134) at junit.framework.Assert.assertEquals(Assert.java:140) at org.apache.commons.dbcp2.TestBasicDataSourceFactory.testProperties(TestBasicDataSourceFactory.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) --
[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=21550&projectId=73 Build statistics: State: Failed Previous State: Failed Started at: Thu 26 Apr 2012 23:20:23 + Finished at: Thu 26 Apr 2012 23:20:45 + Total time: 22s Build Trigger: Schedule Build Number: 108 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_30 Java home: /usr/lib/jvm/jdk1.6.0_30/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: Changed: sebb @ Thu 26 Apr 2012 22:34:46 + Comment: Javadoc Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/AbandonedObjectPool.java ( 1331133 ) Changed: sebb @ Thu 26 Apr 2012 23:09:38 + Comment: Make immutable private fields final Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/PStmtKey.java ( 1331144 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition (Java 1.6) Test Summary: Tests: 0 Failures: 0 Errors: 0 Total time: 0.0 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=21546&projectId=73 Build statistics: State: Failed Previous State: Failed Started at: Thu 26 Apr 2012 20:24:46 + Finished at: Thu 26 Apr 2012 20:24:58 + Total time: 11s Build Trigger: Schedule Build Number: 108 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_30 Java home: /usr/lib/jvm/jdk1.6.0_30/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: org.apache.commons:commons-pool2:2.0-SNAPSHOT Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition (Java 1.6) Test Summary: Tests: 0 Failures: 0 Errors: 0 Total time: 0.0 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math] Question about "AbstractLeastSquaresOptimizer" code
Hi Gilles, > > In revision 1330801, I've added a new "CircleProblem" class (in the "test" > code tree). > It is largely inspired from the existing "CircleVectorial" class but I think > that it might be more representative of the kind of problem people are used > to when dealing with optimizers such as the Levenberg-Marquardt algorithm. > Namely, whereas in "CircleVectorial" the "value" method returns the > residuals, in "CircleProblem" it returns the list of "model" values, i.e. a > list of (x,y) coordinates of points on the circle defined by the 3 given > parameters (center coordinates and radius). That list is the "model" > equivalent of the list returned by "target()" which is the set of "observed" > points (created with "addPoint"). > Also it explicitly introduces the errors on the coordinates of the > "observed" points (see also class "RandomCirclePointGenerator"). > Initially I though that those classes could be useful in setting up a unit > test that would show what to expect from the "guessParametersErrors" method. > But I couldn't figure out how to do it... > Thanks for the hint, I'll look at it. Meanwhile, I've implemented a test based on this reference data set http://www.itl.nist.gov/div898/strd/nls/data/kirby2.shtml The great asset of the NIST data is that it provides expected values of the parameters, as well as their variance. For the time being, we are very close to the reference values... which is a good news... For a while, I thought I had a problem, but that's because in the data file, the points (x, y) are listed in columns, and the first column is... y, not x!!! That's a bit naughty, isn't it! Best regards, Sébastien - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=21541&projectId=73 Build statistics: State: Failed Previous State: Failed Started at: Thu 26 Apr 2012 17:20:22 + Finished at: Thu 26 Apr 2012 17:20:46 + Total time: 23s Build Trigger: Schedule Build Number: 108 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_30 Java home: /usr/lib/jvm/jdk1.6.0_30/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: Changed: sebb @ Thu 26 Apr 2012 16:23:02 + Comment: Add Utility class Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/Utils.java ( 1330927 ) Changed: sebb @ Thu 26 Apr 2012 16:29:17 + Comment: Catch all Exceptions here Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/Utils.java ( 1330930 ) Changed: sebb @ Thu 26 Apr 2012 16:32:44 + Comment: Document thread-safety Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/managed/LocalXAConnectionFactory.java ( 1330935 ) Changed: sebb @ Thu 26 Apr 2012 16:33:06 + Comment: DBCP-322 CPDSConnectionFactory.validateObject(Object) ignores Throwable Files changed: /commons/proper/dbcp/trunk/src/changes/changes.xml ( 1330937 ) /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/BasicDataSource.java ( 1330937 ) /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/CPDSConnectionFactory.java ( 1330937 ) /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/KeyedCPDSConnectionFactory.java ( 1330937 ) /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/managed/BasicManagedDataSource.java ( 1330937 ) Changed: sebb @ Thu 26 Apr 2012 16:40:02 + Comment: Javadoc Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/BasicDataSource.java ( 1330941 ) Changed: sebb @ Thu 26 Apr 2012 16:52:20 + Comment: Make private immutable fields final Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/cpdsadapter/PStmtKeyCPDS.java ( 1330960 ) Changed: sebb @ Thu 26 Apr 2012 16:55:50 + Comment: Make private immutable fields final Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/datasources/CPDSConnectionFactory.java ( 1330965 ) Changed: sebb @ Thu 26 Apr 2012 17:04:29 + Comment: No loss of function by making the username field private, as it has public getter and setter Files changed: /commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp2/managed/DataSourceXAConnectionFactory.java ( 1330972 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition (Java 1.6) Test Summary: Tests: 0 Failures: 0 Errors: 0 Total time: 0.0 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[continuum] BUILD FAILURE: Apache Commons - Commons DBCP - Default Maven 2 Build Definition (Java 1.6)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=21539&projectId=73 Build statistics: State: Failed Previous State: Failed Started at: Thu 26 Apr 2012 16:20:19 + Finished at: Thu 26 Apr 2012 16:20:40 + Total time: 20s Build Trigger: Schedule Build Number: 108 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_30 Java home: /usr/lib/jvm/jdk1.6.0_30/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: Changed: sebb @ Thu 26 Apr 2012 16:11:08 + Comment: Update to latest plugins and dependencies Files changed: /commons/proper/dbcp/trunk/pom.xml ( 1330918 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition (Java 1.6) Test Summary: Tests: 0 Failures: 0 Errors: 0 Total time: 0.0 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math] maven: Problem with "clirr"
On 26 April 2012 13:42, Gilles Sadowski wrote: > Hi. > >> > [...] >> > Here the stack trace from maven output: >> > ---CUT--- >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on >> > project commons-math3: Execution default-site of goal >> > org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 -> [Help 1] >> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> > goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on >> > project commons-math3: Execution default-site of goal >> > org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 >> > at >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) >> > at >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> > at >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> > at >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> > at >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> > at >> > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> > at >> > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) >> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> > at >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> > at >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> > at java.lang.reflect.Method.invoke(Method.java:601) >> > at >> > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> > at >> > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> > at >> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> > at >> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution >> > default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site >> > failed: 780 >> > at >> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) >> > at >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> > ... 19 more >> > Caused by: java.lang.ArrayIndexOutOfBoundsException: 780 >> > at >> > org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:666) >> > at >> > org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:679) >> > at >> > org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:263) >> > at >> > org.codehaus.mojo.clirr.ClirrReport.doReport(ClirrReport.java:243) >> > at >> > org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:219) >> > at >> > org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:355) >> > at >> > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:228) >> > at >> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) >> > at >> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) >> > at >> > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) >> > at >> > org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) >> > at >> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) >> > ... 20 more >> > ---CUT--- >> > >> > Does anyone have an idea of what can cause this? >> >> Yep, that's a bug in the clirr-maven-plugin that was fixed in the latest >> release. >> Please use version 2.4 of clirr-maven-plugin. >> > > Indeed, unless I'm mistaken, we use 2.3 (parent-24). > Shall we upgrade to avoid running into this bug? Already done in CP 25-SNAPSHOT. > > Regards, > Gilles > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e
[GUMP@vmgump]: Project commons-exec-test (in module apache-commons) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-exec-test has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-exec-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/exec/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/exec/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/gump_work/build_apache-commons_commons-exec-test.html Work Name: build_apache-commons_commons-exec-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 24 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/exec] M2_HOME: /opt/maven2 - Running org.apache.commons.exec.util.StringUtilTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.exec.util.MapUtilTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.exec.DefaultExecutorTest FOO.. org.apache.commons.exec.ExecuteException: Process exited with an error: 143 (Exit value: 143) Process completed in 2012 millis; below is its output Process timed out and was killed. Executing [sh, -c, src/test/scripts/invoker.sh] invoker.sh -- going to start daemon process invoker.sh -- daemon process was started cd: 21: can't cd to ../../../target Process completed in 8033 millis; above is its output Processes terminated: 6 killed: 0 Multiplier: 1 MaxRetries: 180 Elapsed (avg ms): 1008 Preparing to execute process - commandLine=[/bin/ls, /opt] Process spun off successfully - process=/bin/ls PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.023 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.025 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.028 ms Process completed in 2005 millis; below is its output Process timed out and was killed by watchdog. gdal_translate HDF5:"/home/kk/grass/data/4404.he5"://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif FOO.. Preparing to execute process - commandLine=[/bin/ls, /opt] Process spun off successfully - process=/bin/ls Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.805 sec <<< FAILURE! Results : Failed tests: testExec_60(org.apache.commons.exec.DefaultExecutorTest) Tests run: 95, Failures: 1, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/exec/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 22 seconds [INFO] Finished at: Thu Apr 26 13:54:27 UTC 2012 [INFO] Final Memory: 25M/65M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 06001226042012, vmgump.apache.org:vmgump:06001226042012 Gump E-mail Identifier (unique within run) #1. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math] maven: Problem with "clirr"
Hi. > > [...] > > Here the stack trace from maven output: > > ---CUT--- > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on > > project commons-math3: Execution default-site of goal > > org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > > goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on > > project commons-math3: Execution default-site of goal > > org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 > > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:601) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > > at > > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > > default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site > > failed: 780 > > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > > ... 19 more > > Caused by: java.lang.ArrayIndexOutOfBoundsException: 780 > > at > > org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:666) > > at > > org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:679) > > at > > org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:263) > > at > > org.codehaus.mojo.clirr.ClirrReport.doReport(ClirrReport.java:243) > > at > > org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:219) > > at > > org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:355) > > at > > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:228) > > at > > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) > > at > > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) > > at > > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) > > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > > ... 20 more > > ---CUT--- > > > > Does anyone have an idea of what can cause this? > > Yep, that's a bug in the clirr-maven-plugin that was fixed in the latest > release. > Please use version 2.4 of clirr-maven-plugin. > Indeed, unless I'm mistaken, we use 2.3 (parent-24). Shall we upgrade to avoid running into this bug? Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
Not your last one, the one before. It ends with:
"One question. When I"
and there's nothing after it.
On Thu, Apr 26, 2012 at 2:31 PM, Gary Lucas wrote:
> Excellent again! Much better.
>
> I'm not sure how that last email got cut short, but you've answered my
> question. So thanks.
>
>
>
> g.
>
>
>
> -Original Message-
> From: Damjan Jovanovic [mailto:damjan@gmail.com]
> Sent: Thursday, April 26, 2012 8:26 AM
> To: Commons Developers List
> Subject: Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
>
> On Thu, Apr 26, 2012 at 2:16 PM, Gary Lucas wrote:
>>
>> Since we're on the subject, another question. In encoding data, I was
>> constructing field types and coding the information. But it looks
>> like you've got some static declarations for doing the same thing.
>> Could you verify that the following is your intended approach
>>
>> public TiffOutputField encodeASCII(TagInfo tInfo, String string)
>> throws ImageWriteException, ImageWriteException
>> {
>> // previous approach:
>> // FieldType fType = new FieldTypeAscii(2, "ASCII");
>> // byte bytes[] = fType.writeData(string, byteOrder);
>>
>> byte bytes[] = FieldType.FIELD_TYPE_ASCII.writeData(string,
>> byteOrder);
>>
>> TiffOutputField tiffOutputField =
>> new TiffOutputField(
>> tInfo.tag,
>> tInfo,
>> FieldType.FIELD_TYPE_ASCII,
>> bytes.length,
>> bytes);
>> return tiffOutputField;
>> }
>
> Do your emails keep getting cut short?
>
> The easiest way, for a known tag type, is:
>
> tiffOutputDirectory.add(TiffTagConstants.TIFF_TAG_DATE_TIME,
> "2012-04-25 01:23:45");
>
> which supports IDE code completion, and automatically overloads to the
> correct method based on the tag type.
>
> For an unknown tag type, I think you have to use the old way where you
> construct a TiffOutputField yourself.
>
> Damjan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
RE: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
Excellent again! Much better.
I'm not sure how that last email got cut short, but you've answered my
question. So thanks.
g.
-Original Message-
From: Damjan Jovanovic [mailto:damjan@gmail.com]
Sent: Thursday, April 26, 2012 8:26 AM
To: Commons Developers List
Subject: Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
On Thu, Apr 26, 2012 at 2:16 PM, Gary Lucas wrote:
>
> Since we're on the subject, another question. In encoding data, I was
> constructing field types and coding the information. But it looks
> like you've got some static declarations for doing the same thing.
> Could you verify that the following is your intended approach
>
> public TiffOutputField encodeASCII(TagInfo tInfo, String string)
> throws ImageWriteException, ImageWriteException
> {
> // previous approach:
> // FieldType fType = new FieldTypeAscii(2, "ASCII");
> // byte bytes[] = fType.writeData(string, byteOrder);
>
> byte bytes[] = FieldType.FIELD_TYPE_ASCII.writeData(string,
> byteOrder);
>
> TiffOutputField tiffOutputField =
> new TiffOutputField(
> tInfo.tag,
> tInfo,
> FieldType.FIELD_TYPE_ASCII,
> bytes.length,
> bytes);
> return tiffOutputField;
> }
Do your emails keep getting cut short?
The easiest way, for a known tag type, is:
tiffOutputDirectory.add(TiffTagConstants.TIFF_TAG_DATE_TIME,
"2012-04-25 01:23:45");
which supports IDE code completion, and automatically overloads to the correct
method based on the tag type.
For an unknown tag type, I think you have to use the old way where you
construct a TiffOutputField yourself.
Damjan
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math] Question about "AbstractLeastSquaresOptimizer" code
On Wed, Apr 25, 2012 at 05:56:32PM +0200, Sébastien Brisard wrote: > 2012/4/25 Gilles Sadowski : > > On Wed, Apr 25, 2012 at 03:46:58PM +0200, Sébastien Brisard wrote: > >> Hi Gillles, > >> > > >> > Can we then agree that the current naming is not really clear? > >> > Since we are not allowed to readily remove this method, the best solution > >> > would be to update the Javadoc to make it clear what is done there, i.e. > >> > cite the full definition of ASE (together with a reference). > >> > > >> this would be the best solution in my view. I just need to find a good > >> reference where ASE is properly defined. > > > > The ones you found are good enough, I guess; just to let people know that > > they might not want to use that method. ;-) > > > Oh no, they do want to use this method. From what I gathered, it's > actually the standard way of estimating the error on the parameters. I > found two nice references > 1. http://www.itl.nist.gov/div898/strd/ (NIST is your friend -- will > implement some unit tests based on these reference cases!) > 2. http://en.wikipedia.org/wiki/Least_squares see paragraph "In a > least squares calculation with unit weights, or in linear regression, > the variance on the jth parameter" In revision 1330801, I've added a new "CircleProblem" class (in the "test" code tree). It is largely inspired from the existing "CircleVectorial" class but I think that it might be more representative of the kind of problem people are used to when dealing with optimizers such as the Levenberg-Marquardt algorithm. Namely, whereas in "CircleVectorial" the "value" method returns the residuals, in "CircleProblem" it returns the list of "model" values, i.e. a list of (x,y) coordinates of points on the circle defined by the 3 given parameters (center coordinates and radius). That list is the "model" equivalent of the list returned by "target()" which is the set of "observed" points (created with "addPoint"). Also it explicitly introduces the errors on the coordinates of the "observed" points (see also class "RandomCirclePointGenerator"). Initially I though that those classes could be useful in setting up a unit test that would show what to expect from the "guessParametersErrors" method. But I couldn't figure out how to do it... Best, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
On Thu, Apr 26, 2012 at 2:16 PM, Gary Lucas wrote:
>
> Since we're on the subject, another question. In encoding data, I was
> constructing field types and coding the information. But it looks like
> you've got some static declarations for doing the same thing. Could you
> verify that the following is your intended approach
>
> public TiffOutputField encodeASCII(TagInfo tInfo, String string)
> throws ImageWriteException, ImageWriteException
> {
> // previous approach:
> // FieldType fType = new FieldTypeAscii(2, "ASCII");
> // byte bytes[] = fType.writeData(string, byteOrder);
>
> byte bytes[] = FieldType.FIELD_TYPE_ASCII.writeData(string, byteOrder);
>
> TiffOutputField tiffOutputField =
> new TiffOutputField(
> tInfo.tag,
> tInfo,
> FieldType.FIELD_TYPE_ASCII,
> bytes.length,
> bytes);
> return tiffOutputField;
> }
Do your emails keep getting cut short?
The easiest way, for a known tag type, is:
tiffOutputDirectory.add(TiffTagConstants.TIFF_TAG_DATE_TIME,
"2012-04-25 01:23:45");
which supports IDE code completion, and automatically overloads to the
correct method based on the tag type.
For an unknown tag type, I think you have to use the old way where you
construct a TiffOutputField yourself.
Damjan
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
RE: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
Since we're on the subject, another question. In encoding data, I was
constructing field types and coding the information. But it looks like you've
got some static declarations for doing the same thing. Could you verify that
the following is your intended approach
public TiffOutputField encodeASCII(TagInfo tInfo, String string)
throws ImageWriteException, ImageWriteException
{
// previous approach:
//FieldType fType = new FieldTypeAscii(2, "ASCII");
//byte bytes[] = fType.writeData(string, byteOrder);
byte bytes[] = FieldType.FIELD_TYPE_ASCII.writeData(string, byteOrder);
TiffOutputField tiffOutputField =
new TiffOutputField(
tInfo.tag,
tInfo,
FieldType.FIELD_TYPE_ASCII,
bytes.length,
bytes);
return tiffOutputField;
}
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
RE: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
Excellent idea. Thanks.
Our application uses a modified version of Sanselan that includes my
performance enhancements. I've started swapping that out with the latest from
Apache Imaging, again with my latest two patches for speed improvements. On
the read side, it went very quickly. On the write side, I'm still trying to
get things working. Although the API is definitely a lot cleaner than the
original, I'm not sure I've figured it out yet.
Here's a snippet of code I'm using to write a GeoTIFF file. Would you take a
look and make sure I am doing the right thing (particularly in the constructor
for the TiffOutputDirectory)? The fieldList is a set of output fields that
were populated by a utility routine. That approach is a hold-over from the
Sanselan implementation (is there a better way to do it?). I add them to an
output directory, bundle the directory in an output set, and pass the output
set into the lossy writer as a parameter.
HashMap params = new HashMap();
// set optional parameters if you like
params.put(ImagingConstants.PARAM_KEY_COMPRESSION,
new Integer(TiffConstants.TIFF_COMPRESSION_UNCOMPRESSED));
// tiffByteOrder set as appropriate for system
// fieldList is an array list of TiffOutputFields that
// was set by a utility class.
TiffImageWriterLossy lWriter =
new TiffImageWriterLossy(tiffByteOrder);
TiffOutputDirectory tiffDirectory = new TiffOutputDirectory(
TiffDirectoryConstants.DIRECTORY_TYPE_DIR_0, tiffByteOrder);
for (TiffOutputField field : fieldList) {
tiffDirectory.add(field);
}
TiffOutputSet tiffOutputSet = new TiffOutputSet();
tiffOutputSet.addDirectory(tiffDirectory);
params.put(ImagingConstants.PARAM_KEY_EXIF, tiffOutputSet);
FileOutputStream fos = new FileOutputStream(outputFile);
BufferedOutputStream bos = new BufferedOutputStream(fos);
lWriter.writeImage(outputImage, bos, params);
bos.flush();
bos.close();
fos.close();
One question. When I
-Original Message-
From: Damjan Jovanovic [mailto:damjan@gmail.com]
Sent: Thursday, April 26, 2012 12:02 AM
To: Commons Developers List
Subject: Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
On Wed, Apr 25, 2012 at 10:30 PM, Gary Lucas wrote:
> I'm taking a stab at transitioning from Sanselan to the new Apache Imaging.
> One thing I've noticed is that one of the EXIF tags my existing software uses
> seems to have been removed from imaging:
>
> public static final TagInfo EXIF_TAG_MODIFY_DATE = new TagInfo(
> "Modify Date", 0x0132, FIELD_TYPE_ASCII, 1,
> EXIF_DIRECTORY_IFD0);
>
>
> I'm not familiar with the details behind this tag. Was it removed because
> it is obsolete or non-standard? An oversight?
>
> Thanks.
>
> Gary
One of the recent changes was deduplication of TIFF tags, and grouping of tags
by specification.
Tag 0x0132 is defined in the TIFF6 specification, so it is now under
TiffTagConstants, and known as TIFF_TAG_DATE_TIME.
Also I am considering replacing the EXIF_ prefix with TIFF_ for all tags.
Damjan
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
