[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 48 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-scxml-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-WARNING- Overriding Maven settings:
[/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml]
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/scxml/pom.xml
-INFO- Project Reports in:
/srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html
Work Name: build_apache-commons_commons-scxml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 19 secs
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.139 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 misplaced 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 foo 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 bar 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 datamodel 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 data 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 baz 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.063 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]
[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 30 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-22062012.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 Jun 22 07:49:34 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 1422062012, vmgump.apache.org:vmgump:1422062012 Gump E-mail Identifier (unique within run) #46. -- 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: [VFS] Feedback on VFS-422 please
Gary, The S3 provider has an implementation https://github.com/abashev/vfs-s3/tree/master/src/main/java/com/intridea/io/vfs/provider/s3/operations You'd probably need to talk with Mario about specifics. From what I can tell, it's basically an implementation of the Command pattern with the implementations registered in the concrete implementation FileOperationsProvider interface. This basically let's you ask what operations are available from this file system, you can then select and invoke the operation that you want. The original idea was that you would be able to use it with SVN, or other version control systems, but also with Sanselan ( http://wiki.apache.org/commons/VfsNext). But the SVN implementation seems to be blocked now due to licensing issues: https://issues.apache.org/jira/browse/VFS-43. I don't know of any other implementations (other than S3) attempting to use it, but I would imagine that it would be pretty useful. Mark On Thu, Jun 21, 2012 at 5:59 PM, Gary Gregory garydgreg...@gmail.comwrote: On Thu, Jun 21, 2012 at 6:38 PM, Ralph Goers ralph.go...@dslextreme.com wrote: On Jun 21, 2012, at 2:41 PM, Gary Gregory wrote: On Thu, Jun 21, 2012 at 5:10 PM, Mark Fortner phidia...@gmail.com wrote: Gary, There was some talk a while back about implementing File System-specific Operations. I think what Mario had in mind was supporting version control system functionality through VFS. It strikes me that this might be the best way for implementing functionality that makes use of the JSch bells and whistles without breaking encapsulation. Hi Mark, I am not sure I understand what you are proposing. Look at the org.apache.commons.vfs2.operations package. hm... ok, I do not see any implementers of this package. Where is there an example? I assume that this can be used to implement this new feature. What would that look like? Thank you, Gary Ralph - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0 Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: [VFS] Feedback on VFS-422 please
I'm not sure why SVN support would require the operations stuff. I actually implemented an SVN provider at one point but didn't commit it here due to the svnkit license. Ralph On Jun 22, 2012, at 7:49 AM, Mark Fortner wrote: Gary, The S3 provider has an implementation https://github.com/abashev/vfs-s3/tree/master/src/main/java/com/intridea/io/vfs/provider/s3/operations You'd probably need to talk with Mario about specifics. From what I can tell, it's basically an implementation of the Command pattern with the implementations registered in the concrete implementation FileOperationsProvider interface. This basically let's you ask what operations are available from this file system, you can then select and invoke the operation that you want. The original idea was that you would be able to use it with SVN, or other version control systems, but also with Sanselan ( http://wiki.apache.org/commons/VfsNext). But the SVN implementation seems to be blocked now due to licensing issues: https://issues.apache.org/jira/browse/VFS-43. I don't know of any other implementations (other than S3) attempting to use it, but I would imagine that it would be pretty useful. Mark On Thu, Jun 21, 2012 at 5:59 PM, Gary Gregory garydgreg...@gmail.comwrote: On Thu, Jun 21, 2012 at 6:38 PM, Ralph Goers ralph.go...@dslextreme.com wrote: On Jun 21, 2012, at 2:41 PM, Gary Gregory wrote: On Thu, Jun 21, 2012 at 5:10 PM, Mark Fortner phidia...@gmail.com wrote: Gary, There was some talk a while back about implementing File System-specific Operations. I think what Mario had in mind was supporting version control system functionality through VFS. It strikes me that this might be the best way for implementing functionality that makes use of the JSch bells and whistles without breaking encapsulation. Hi Mark, I am not sure I understand what you are proposing. Look at the org.apache.commons.vfs2.operations package. hm... ok, I do not see any implementers of this package. Where is there an example? I assume that this can be used to implement this new feature. What would that look like? Thank you, Gary Ralph - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0 Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VFS] Feedback on VFS-422 please
I think the idea was to implement functionality that doesn't fit with what File Systems do, in this version control system operations. So that operations like update, commit, revert, etc could be supported. I too, implemented something on top of SVNKit (for an internal project), and another project on top of YANNFS -- I wonder how many implementations are floating around there just due to licensing restrictions? Mark On Fri, Jun 22, 2012 at 10:06 AM, Ralph Goers ralph.go...@dslextreme.comwrote: I'm not sure why SVN support would require the operations stuff. I actually implemented an SVN provider at one point but didn't commit it here due to the svnkit license. Ralph On Jun 22, 2012, at 7:49 AM, Mark Fortner wrote: Gary, The S3 provider has an implementation https://github.com/abashev/vfs-s3/tree/master/src/main/java/com/intridea/io/vfs/provider/s3/operations You'd probably need to talk with Mario about specifics. From what I can tell, it's basically an implementation of the Command pattern with the implementations registered in the concrete implementation FileOperationsProvider interface. This basically let's you ask what operations are available from this file system, you can then select and invoke the operation that you want. The original idea was that you would be able to use it with SVN, or other version control systems, but also with Sanselan ( http://wiki.apache.org/commons/VfsNext). But the SVN implementation seems to be blocked now due to licensing issues: https://issues.apache.org/jira/browse/VFS-43. I don't know of any other implementations (other than S3) attempting to use it, but I would imagine that it would be pretty useful. Mark On Thu, Jun 21, 2012 at 5:59 PM, Gary Gregory garydgreg...@gmail.com wrote: On Thu, Jun 21, 2012 at 6:38 PM, Ralph Goers ralph.go...@dslextreme.com wrote: On Jun 21, 2012, at 2:41 PM, Gary Gregory wrote: On Thu, Jun 21, 2012 at 5:10 PM, Mark Fortner phidia...@gmail.com wrote: Gary, There was some talk a while back about implementing File System-specific Operations. I think what Mario had in mind was supporting version control system functionality through VFS. It strikes me that this might be the best way for implementing functionality that makes use of the JSch bells and whistles without breaking encapsulation. Hi Mark, I am not sure I understand what you are proposing. Look at the org.apache.commons.vfs2.operations package. hm... ok, I do not see any implementers of this package. Where is there an example? I assume that this can be used to implement this new feature. What would that look like? Thank you, Gary Ralph - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0 Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r1351831 - /commons/proper/configuration/tags/CONFIGURATION_1_8/
Am 21.06.2012 18:36, schrieb sebb: On 21 June 2012 17:18, sebb seb...@gmail.com wrote: On 20 June 2012 20:25, Oliver Heger oliver.he...@oliver-heger.de wrote: Am 20.06.2012 00:18, schrieb sebb: On 19 June 2012 21:11,ohe...@apache.org wrote: Author: oheger Date: Tue Jun 19 20:11:15 2012 New Revision: 1351831 URL: http://svn.apache.org/viewvc?rev=1351831view=rev Log: Created tag for Configuration 1.8 release. Added: commons/proper/configuration/tags/CONFIGURATION_1_8/ (props changed) - copied from r1351829, commons/proper/configuration/tags/CONFIGURATION_1_8RC1/ The tag should be an exact copy. Dunno how you created the copy, but it should not have changes such as the ones below. I executed the command below (copied from my command line history). How can this cause a diff? It looks like as if the value of the svn:ignore property is dumped which is already set for trunk (?). Oliver svn copy https://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_1_8RC1/ https://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_1_8 -m Created tag for Configuration 1.8 release. Thanks, that looks fine. I just tried creating a dummy tag and the commit message showed the same apparent property changes. Dunno what is going on here. I might try asking on the subversion list. Just had a look at the commit mail from creating the MATH tag r1352195 - /commons/proper/math/tags/MATH_3_0/ This does not exhibit the same behaviour. Yes, I noticed, too. One difference is that the original MATH tag does not have an svn:mergeinfo property, whereas the configuration tag does. Maybe that is causing the differences in the e-mail. I checked the property listings for CONFIGURATION_1_8RC1 and CONFIGURATION_1_8 and they are the same. Strange. So at least, the content of the copy does not differ from its source. I remember that I saw similar diffs a while ago when I moved folders around during refactoring operations at work. That time I thought it might have something to do with svn version differences between client and server because I just switched to 1.7. Oliver Propchange: commons/proper/configuration/tags/CONFIGURATION_1_8/ -- --- svn:ignore (added) +++ svn:ignore Tue Jun 19 20:11:15 2012 @@ -0,0 +1,16 @@ +*~ +*.iws +*.ipr +*.iml +.* +docs +target +test-reports +velocity.log* +maven.log +STRING0 +lib +*.ser +junit*.properties +*.patch +maven-eclipse.xml Propchange: commons/proper/configuration/tags/CONFIGURATION_1_8/ -- --- svn:mergeinfo (added) +++ svn:mergeinfo Tue Jun 19 20:11:15 2012 @@ -0,0 +1 @@ +/commons/proper/configuration/branches/CONFIGURATION_390:819412-822131 - 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: [VFS] Feedback on VFS-422 please
I ended up adding versioning support for WebDAV without using operations. Now you have me wondering if I should have used it. Ralph On Jun 22, 2012, at 10:59 AM, Mark Fortner wrote: I think the idea was to implement functionality that doesn't fit with what File Systems do, in this version control system operations. So that operations like update, commit, revert, etc could be supported. I too, implemented something on top of SVNKit (for an internal project), and another project on top of YANNFS -- I wonder how many implementations are floating around there just due to licensing restrictions? Mark On Fri, Jun 22, 2012 at 10:06 AM, Ralph Goers ralph.go...@dslextreme.comwrote: I'm not sure why SVN support would require the operations stuff. I actually implemented an SVN provider at one point but didn't commit it here due to the svnkit license. Ralph On Jun 22, 2012, at 7:49 AM, Mark Fortner wrote: Gary, The S3 provider has an implementation https://github.com/abashev/vfs-s3/tree/master/src/main/java/com/intridea/io/vfs/provider/s3/operations You'd probably need to talk with Mario about specifics. From what I can tell, it's basically an implementation of the Command pattern with the implementations registered in the concrete implementation FileOperationsProvider interface. This basically let's you ask what operations are available from this file system, you can then select and invoke the operation that you want. The original idea was that you would be able to use it with SVN, or other version control systems, but also with Sanselan ( http://wiki.apache.org/commons/VfsNext). But the SVN implementation seems to be blocked now due to licensing issues: https://issues.apache.org/jira/browse/VFS-43. I don't know of any other implementations (other than S3) attempting to use it, but I would imagine that it would be pretty useful. Mark On Thu, Jun 21, 2012 at 5:59 PM, Gary Gregory garydgreg...@gmail.com wrote: On Thu, Jun 21, 2012 at 6:38 PM, Ralph Goers ralph.go...@dslextreme.com wrote: On Jun 21, 2012, at 2:41 PM, Gary Gregory wrote: On Thu, Jun 21, 2012 at 5:10 PM, Mark Fortner phidia...@gmail.com wrote: Gary, There was some talk a while back about implementing File System-specific Operations. I think what Mario had in mind was supporting version control system functionality through VFS. It strikes me that this might be the best way for implementing functionality that makes use of the JSch bells and whistles without breaking encapsulation. Hi Mark, I am not sure I understand what you are proposing. Look at the org.apache.commons.vfs2.operations package. hm... ok, I do not see any implementers of this package. Where is there an example? I assume that this can be used to implement this new feature. What would that look like? Thank you, Gary Ralph - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: http://goog_1249600977http://bit.ly/ECvg0 Spring Batch in Action: http://s.apache.org/HOqhttp://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[configuration] Thoughts about a new version
Hi, there is a request [1] to publish a release of [configuration] which is compatible with the newest version of [lang]. This really makes sense, I am myself in a situation where I have to include [lang] in two versions (2.x and 3.x) due to the dependency to [configuration]. Unfortunately, switching to [lang] 3.x cannot be done in a binary compatible way because some types are exposed in the public API of [configuration]. I doubt that we will come up with a revised and clean version of a Configuration 2.0 API sometime soon. So what are our options? Should we push out an intermediate 2.0 version which is pretty close to the current trunk with some incompatible changes? (What other improvements could such a version contain which can be implemented with a reasonable effort?) The major API redesign would then be done for version 3.0. IMHO this would fit well to the release early/release often paradigm. Independent from this, it would be good to start a discussion about how a next-generation configuration API could look like. What are your opinions? Oliver [1] https://issues.apache.org/jira/browse/CONFIGURATION-462 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-jxpath (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-jxpath has an issue affecting its community integration. This issue affects 4 projects, and has been outstanding for 38 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - ant-embed-optional : Historical Embed Proposal for Ant - commons-jxpath : XPath traversal of JavaBeans - forrest-test : Apache Forrest software is a publishing framework that trans... - forrest-test-basic : Apache Forrest software is a publishing framework that trans... Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-jxpath/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-jxpath.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-jxpath/gump_work/build_apache-commons_commons-jxpath.html Work Name: build_apache-commons_commons-jxpath (Type: Build) Work ended in a state of : Failed Elapsed: 45 secs Command Line: /usr/lib/jvm/java-6-openjdk/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:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-23062012.jar -Djaxp.xslt.jar=/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar -Dj2ee.jar=/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar -Djaxp.jaxp.jar=/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar -Dcomponent.version=23062012 dist [Working Directory: /srv/gump/public/workspace/apache-commons/jxpath] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/apache-commons/jxpath/target/classes:/srv/gump/public/workspace/apache-commons/jxpath/target/test-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/ant/bootstrap/lib/ant.jar:/srv/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-23062012.jar:/srv/gump/packages/apache-attic/avalon-logkit-2.1.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons -collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/commons-lang-2.x/target/commons-lang-2.7-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-23062012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-23062012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-23062012.jar:/srv/gump/packages/mockrunner-0.4/lib/jdk1.5/jee5/mockrunner-servlet.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar:/srv/gump/public/workspace/junit/dist/junit-23062012.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar - [junit] Testcase: testAxisFollowing took 0.004 sec [junit] Testcase: testIteratePropertyArrayWithHasNext took 0 sec [junit] Testcase: testRemoveAllListElements took 0.001 sec [junit] Testcase: testRelativeContextParent took 0.001 sec [junit] Testcase: testAxisChildNestedCollection took 0.001 sec [junit] Testcase: testAxisSelf took 0.001 sec [junit] Testcase: testCreatePathCreateBeanExpandCollection took 0 sec [junit] Testcase: testRelativeContextRelativePath took 0.001 sec [junit] Testcase: testAttributeLang took 0.001 sec [junit] Testcase: testAttributeName took 0.001 sec [junit] Testcase: testCreatePathAndSetValue took 0.001 sec [junit] Testcase: testCoreFunctions took 0.008 sec [junit] Testcase: testCreatePath took 0.001 sec [junit] Testcase: testRemoveAllMapEntries took 0.001 sec [junit] Testcase: testBooleanPredicate took 0.039 sec [junit] Testcase: testRemovePathArrayElement
[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 38 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-digester3 : XML to Java Object Configuration
- commons-digester3-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [commons-digester3-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/digester/pom.xml
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Failed
Elapsed: 45 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: 1340418284357
[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.annotations.processor.GeneratedRulesModule
error:
[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 193 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: 14 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.GraphConnectionjava.lang.Object,java.lang.Object) in org.apache.commons.graph.builder.LinkedConnectionBuilderjava.lang.Object,java.lang.Object,org.apache.commons.graph.model.UndirectedMutableGraphV,E cannot be applied to (org.apache.commons.graph.builder.GraphConnectionV,E) [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.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [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.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [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.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [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.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/spanning/DefaultSpanningTreeSourceSelector.java:[109,20] W,MwhereEdgesHaveWeights(M) in org.apache.commons.graph.shortestpath.PathWeightedEdgesBuilderjava.lang.Object,java.lang.Object cannot be applied to (org.apache.commons.graph.MapperWE,W) [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/connectivity/DefaultConnectivityAlgorithmsSelector.java:[69,64] cannot find symbol symbol
[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 38 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-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.003 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 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.044 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.018 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 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.019 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.179 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 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.014 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: Sat Jun 23 03:59:58 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:
