BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 3 notifys should have been sent *** G U M P [g...@vmgump]: Project maven (in module maven) failed [g...@vmgump]: Project maven-bootstrap (in module maven) failed [g...@vmgump]: Project portals-pluto-portal-1.0 (in module portals-pluto-1.0) failed *** G U M P [g...@vmgump]: Project maven (in module maven) 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 maven 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: - maven : Project Management Tools Full details are available at: http://vmgump.apache.org/gump/public/maven/maven/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [maven-15032010.jar] identifier set to project name -INFO- Made directory [/srv/gump/public/workspace/maven/target/classes] -INFO- Made directory [/srv/gump/public/workspace/maven/target/test-classes] -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/maven/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/maven/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/maven/project.properties -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/maven/maven/gump_work/build_maven_maven.html Work Name: build_maven_maven (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/maven] CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/maven/target/classes:/srv/gump/public/workspace/maven/target/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.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/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-15032010.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-15032010.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/digester/dist/commons-digester.jar:/srv/gump/public/workspace/commons-dormant/graph2/target /commons-graph-15032010.jar:/srv/gump/public/workspace/httpcomponents/oac.hc3x/dist/commons-httpclient.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.0-SNAPSHOT.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-15032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-15032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-15032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/util/target/commons-jelly-tags-util-15032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-15032010.jar:/srv/gump/public/workspace/apache-commons/jexl/target/commons-jexl-2.0.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/lang/target/commons-lang-3.0-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-15032010.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-lo gging-api-15032010.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-15032010.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xpp/build/xpp3-15032010.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependencies: jaxen-1.1-beta-9.jar ant-trax-1.6.5.jar (try downloading from http://ant.apache.org/) commons-codec-1.2.jar (try downloading from http://commons.apache.org/codec/) xercesImpl-2.8.0.jar (try downloading from http://xerces.apache.org/xerces2-j/) plexus-utils-1.0.5.jar maven-
Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml
-- From: "Stefan Bodewig" Sent: Monday, March 15, 2010 8:01 AM To: Subject: Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml On 2010-03-15, Bill Barker wrote: -- From: "Stefan Bodewig" Sent: Sunday, March 14, 2010 10:20 PM To: Subject: Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml On 2010-03-13, Bill Barker wrote: Yeah, downloaded the src distro for maven 2.2.1, and it is that it is that the 'central' repo is disabled for SNAPSHOTs (and it is looking for a SNAPSHOT POM). So Maven never asks to get it (even though it is there). Do I understand this correctly that with Maven 2.2 Gump will not be able to inject its own jars if the POM specifies a dependency on a SNAPSHOT version? I think that this is a setting for 'central', that it disables SNAPSHOT versions (understandable from the Maven prospective). It's just that Maven won't download a SNAPSHOT version from 'central'. Reactor builds with SNAPSHOT should still work. I see. SNAPSHOTs then will likely be pulled from different repositories and we'd need to make the Maven proxy intercept those as well. Or, like for hudson, they just won't be found. I was thinking of adding a localRepository="name" to the builder that allows projects to share a local repo when they can't be trusted to use the central repo. These would be cleaned when Gump finishes (or maybe on startup). Then the projects could use a goal of 'install', and it looks like Maven will accept it for another project that wants to depend on that SNAPSHOT version. Briefly thought of overriding this in either the local or global settings, but then realized that I don't know enough about Maven to get it right in the first 10 tries ;). That is why I was hoping that there is still a Maven guru lurking here. Same here. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 3 notifys should have been sent *** G U M P [g...@vmgump]: Project maven (in module maven) failed [g...@vmgump]: Project maven-bootstrap (in module maven) failed [g...@vmgump]: Project portals-pluto-portal-1.0 (in module portals-pluto-1.0) failed *** G U M P [g...@vmgump]: Project maven (in module maven) 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 maven 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: - maven : Project Management Tools Full details are available at: http://vmgump.apache.org/gump/public/maven/maven/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [maven-14032010.jar] identifier set to project name -INFO- Made directory [/srv/gump/public/workspace/maven/target/classes] -INFO- Made directory [/srv/gump/public/workspace/maven/target/test-classes] -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/maven/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/maven/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/maven/project.properties -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/maven/maven/gump_work/build_maven_maven.html Work Name: build_maven_maven (Type: Build) Work ended in a state of : Failed Elapsed: 3 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/maven] CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/maven/target/classes:/srv/gump/public/workspace/maven/target/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.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/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-14032010.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-14032010.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/digester/dist/commons-digester.jar:/srv/gump/public/workspace/commons-dormant/graph2/target /commons-graph-14032010.jar:/srv/gump/public/workspace/httpcomponents/oac.hc3x/dist/commons-httpclient.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.0-SNAPSHOT.jar:/srv/gump/public/workspace/commons-jelly/target/commons-jelly-14032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-14032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-14032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/util/target/commons-jelly-tags-util-14032010.jar:/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-14032010.jar:/srv/gump/public/workspace/apache-commons/jexl/target/commons-jexl-2.0.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/lang/target/commons-lang-3.0-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-14032010.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-lo gging-api-14032010.jar:/srv/gump/public/workspace/dom4j/build/dom4j.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-14032010.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xml-commons/java/build/which.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xpp/build/xpp3-14032010.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 The build cannot continue because of the following unsatisfied dependencies: jaxen-1.1-beta-9.jar ant-trax-1.6.5.jar (try downloading from http://ant.apache.org/) commons-codec-1.2.jar (try downloading from http://commons.apache.org/codec/) xercesImpl-2.8.0.jar (try downloading from http://xerces.apache.org/xerces2-j/) plexus-utils-1.0.5.jar maven-
Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml
On 2010-03-15, Bill Barker wrote: > -- > From: "Stefan Bodewig" > Sent: Sunday, March 14, 2010 10:20 PM > To: > Subject: Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml >> On 2010-03-13, Bill Barker wrote: >>> Yeah, downloaded the src distro for maven 2.2.1, and it is that it is >>> that the 'central' repo is disabled for SNAPSHOTs (and it is looking >>> for a SNAPSHOT POM). So Maven never asks to get it (even though it is >>> there). >> Do I understand this correctly that with Maven 2.2 Gump will not be able >> to inject its own jars if the POM specifies a dependency on a SNAPSHOT >> version? > I think that this is a setting for 'central', that it disables > SNAPSHOT versions (understandable from the Maven prospective). It's > just that Maven won't download a SNAPSHOT version from 'central'. > Reactor builds with SNAPSHOT should still work. I see. SNAPSHOTs then will likely be pulled from different repositories and we'd need to make the Maven proxy intercept those as well. > Briefly thought of overriding this in either the local or global > settings, but then realized that I don't know enough about Maven to > get it right in the first 10 tries ;). That is why I was hoping that > there is still a Maven guru lurking here. Same here. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r923057 - /gump/metadata/project/commons-proper.xml
On 2010-03-15, sebb wrote: > On 15/03/2010, Stefan Bodewig wrote: >> On 2010-03-15, sebb wrote: >>> On 15/03/2010, bode...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=923057&view=rev Log: canonical property to skip tests in mvn - > >>> maven.test.skip.exec is deprecated: >>> http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#skipExec >>> which is why I used skipTests. >> I didn't know that and wanted things to be consistent - we use the now >> deprecated version all over the place. >> What is plugin version determined by? The installed mvn version (2.2 by >> now) or the project's POM? > The project POM determines the version, assuming that the POM defines > the version. >> skipTests would require Surefire 2.4 to work >> and I don't know whether this is actually used by all projects. > Good point, but Commons-parent 13 uses 2.5 I've reverted the commons-io project, if it works we can start moving over other occurances of maven.test.skip.exec. It wouldn't be the first mvn property that failed to work as advertised in the Gump context (project.build.finalName is one such example) - it may be that we just don't understand Maven well enough, though. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r923057 - /gump/metadata/project/commons-proper.xml
On 15/03/2010, Stefan Bodewig wrote: > On 2010-03-15, sebb wrote: > > > On 15/03/2010, bode...@apache.org wrote: > > > >> URL: http://svn.apache.org/viewvc?rev=923057&view=rev > >> Log: > >> canonical property to skip tests in mvn > > > >> - > >> + > > > maven.test.skip.exec is deprecated: > > > > http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#skipExec > > > which is why I used skipTests. > > > I didn't know that and wanted things to be consistent - we use the now > deprecated version all over the place. > > What is plugin version determined by? The installed mvn version (2.2 by > now) or the project's POM? The project POM determines the version, assuming that the POM defines the version. > skipTests would require Surefire 2.4 to work > and I don't know whether this is actually used by all projects. Good point, but Commons-parent 13 uses 2.5 Note that skipExec itself requires 2.3, so could cause problems if a project uses an earlier version of surefire. Only "skip" is valid for all versions of Surefire, but that is not ideal. > Stefan > > - > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > For additional commands, e-mail: general-h...@gump.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r923057 - /gump/metadata/project/commons-proper.xml
On 2010-03-15, sebb wrote: > On 15/03/2010, bode...@apache.org wrote: >> URL: http://svn.apache.org/viewvc?rev=923057&view=rev >> Log: >> canonical property to skip tests in mvn >> - >> + > maven.test.skip.exec is deprecated: > http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#skipExec > which is why I used skipTests. I didn't know that and wanted things to be consistent - we use the now deprecated version all over the place. What is plugin version determined by? The installed mvn version (2.2 by now) or the project's POM? skipTests would require Surefire 2.4 to work and I don't know whether this is actually used by all projects. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r923057 - /gump/metadata/project/commons-proper.xml
On 15/03/2010, bode...@apache.org wrote: > Author: bodewig > Date: Mon Mar 15 05:23:18 2010 > New Revision: 923057 > > URL: http://svn.apache.org/viewvc?rev=923057&view=rev > Log: > canonical property to skip tests in mvn > > Modified: > gump/metadata/project/commons-proper.xml > > Modified: gump/metadata/project/commons-proper.xml > URL: > http://svn.apache.org/viewvc/gump/metadata/project/commons-proper.xml?rev=923057&r1=923056&r2=923057&view=diff > > == > --- gump/metadata/project/commons-proper.xml (original) > +++ gump/metadata/project/commons-proper.xml Mon Mar 15 05:23:18 2010 > @@ -449,7 +449,7 @@ > Commons I/O Utility Package > > > - > + maven.test.skip.exec is deprecated: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#skipExec which is why I used skipTests. > > > > > > - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
