Re: build of poi in gump/cleanup might be needed on vmgump
On Fri, 10 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: @Stefan : do you think that gump will pick up my metadata change spontaneously ? Maybe the old svn sandbox of poi should be wiped. I will purge them, just to be sure. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
build of poi in gump : cleanup needed
Hi, the svn sandbox of jakarta-poi and the copy area to which it gets synced too should be cleaned on vmgump. http://vmgump.apache.org/gump/public/jakarta-poi/jakarta-poi/gump_work/build_jakarta-poi_jakarta-poi.html I changed the metadata last night, basically to make the jakarta-poi module build the trunk and not the 2.0 branch any more. Can someone help ? Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build of poi in gump/cleanup might be needed on vmgump
Hello Stefan, thanks, sorry for sending another email with the same subject, I was just anxious that you might have not seen the first one. Regards, Antoine Original-Nachricht Datum: Fri, 10 Nov 2006 20:55:02 +0100 Von: Stefan Bodewig [EMAIL PROTECTED] An: general@gump.apache.org Betreff: Re: build of poi in gump/cleanup might be needed on vmgump On Fri, 10 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: @Stefan : do you think that gump will pick up my metadata change spontaneously ? Maybe the old svn sandbox of poi should be wiped. I will purge them, just to be sure. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Bill Barker [EMAIL PROTECTED] wrote: Actually, we already have the Python part (at least in trunk). Thanks for reminding us, you finally made me scratch one thing from my TODO list. Maven2 is now installed and should be available to the test workspace on it unless I've made any mistakes (which I probably have ;-). Once Gump says it can find mvn in http://gump.zones.apache.org/gump/test/index.html we can use bcel as our test project for the Maven2 support in Gump. bcel doesn't have any dependencies to speak of, so the missing pieces won't hurt too badly. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Installing a fresh gump2 yields lots of issues
On Fri, 10 Nov 2006, Stefano Mazzocchi [EMAIL PROTECTED] wrote: First of all, installing the 'full gump' run without vmgump packages, it's a nightmare, nobody with their sane minds would do it. True. Second, while svn doesn't need this, cvs does require the anonymous user to login if the password is not empty... which means, again, that without vmgump's .cvspass, it would be hell. I thought all our repository information contained passwords for CVS and at least the old Gump would create .cvspass files itself (it's not as if CVS used some string encryption for that file). Doesn't it do that anymore? - jmock: cvs repo seems to be no longer available - cargo: svn: URL 'svn://svn.cargo.codehaus.org/cargo/scm/cargo/trunk' doesn't exist - groovy: /home/projects/groovy/scm: no such repository are known issues, but we are using the official URLs you get from each project's website. - directory-naming: svn: URL 'http://svn.apache.org/repos/asf/directory/trunks/naming' doesn't exist - geronimo: svn: URL 'http://svn.apache.org/repos/asf/geronimo/trunk' doesn't exist - no idea what the Gump-correct URL would be. There are other repositories that are broken as well: xstream, javassist, eyebrowse and beanshell. Problem with stable Gump as opposed to trunk Gump is that it doesn't get flagged as a problem, so I usually look at helios to see whether we have problems the repo information. smartfrog was/is in the process of migrating from CVS to svn and I'd consider the current problem transient - read, Steve is going to fix it once the migration is done. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Stefan Bodewig [EMAIL PROTECTED] wrote: Maven2 is now installed installed on helios AKA gump.zones.apache.org, that is. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: This requires adding in the gump metadata of projects built with ant which are maven dependees the groupId and artifactId of each jar, plus the version that maven wants. version*s* since different Maven projects might ask for different versions. What you describe would either require manually updating all descriptors or making Gump smart enough to parse Maven2 POMs. In an off-list discussion Steve mentioned an idea to me that may even be easier to implement: Create a Web Application that understands Maven's remote repository layout and point mvn to this webapp as the only available repository to use. This webapp would then map the artifact id to the corresponding Gump jar and serve up the latest artifacts from the current build. This way we only need to understand the groupId/artifactId mappings but (1) can ignore the version information completely and (2) don't give mvn a chance to pull in uncontrolled artifacts at all. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
Stefan Bodewig wrote: On Fri, 10 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: This requires adding in the gump metadata of projects built with ant which are maven dependees the groupId and artifactId of each jar, plus the version that maven wants. version*s* since different Maven projects might ask for different versions. What you describe would either require manually updating all descriptors or making Gump smart enough to parse Maven2 POMs. In an off-list discussion Steve mentioned an idea to me that may even be easier to implement: Create a Web Application that understands Maven's remote repository layout and point mvn to this webapp as the only available repository to use. This webapp would then map the artifact id to the corresponding Gump jar and serve up the latest artifacts from the current build. This way we only need to understand the groupId/artifactId mappings but (1) can ignore the version information completely and (2) don't give mvn a chance to pull in uncontrolled artifacts at all. how about following maven1 footsteps: we force maven2 to stay offline and then we use symlinks in the .m2 repo to point at the gump-generated jars? superhacky, but it could work and doesn't require webapp development/management -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Nov 10, 2006, at 12:43 PM, Stefan Bodewig wrote: On Fri, 10 Nov 2006, Stefan Bodewig [EMAIL PROTECTED] wrote: Maven2 is now installed installed on helios AKA gump.zones.apache.org, that is. FWIW Maven2 2.0.2 is also available on Clarus (it's back! it's back!). S. -- [EMAIL PROTECTED]http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF smime.p7s Description: S/MIME cryptographic signature
Re: Installing a fresh gump2 yields lots of issues
Hi Stefan, Stefan Bodewig wrote: On Fri, 10 Nov 2006, Stefano Mazzocchi [EMAIL PROTECTED] wrote: First of all, installing the 'full gump' run without vmgump packages, it's a nightmare, nobody with their sane minds would do it. True. Second, while svn doesn't need this, cvs does require the anonymous user to login if the password is not empty... which means, again, that without vmgump's .cvspass, it would be hell. I thought all our repository information contained passwords for CVS and at least the old Gump would create .cvspass files itself (it's not as if CVS used some string encryption for that file). Doesn't it do that anymore? - jmock: cvs repo seems to be no longer available :pserver:[EMAIL PROTECTED]:/cvs/jmock/ - cargo: svn: URL 'svn://svn.cargo.codehaus.org/cargo/scm/cargo/trunk' doesn't exist - groovy: /home/projects/groovy/scm: no such repository are known issues, but we are using the official URLs you get from each project's website. - directory-naming: svn: URL 'http://svn.apache.org/repos/asf/directory/trunks/naming' doesn't exist - geronimo: svn: URL 'http://svn.apache.org/repos/asf/geronimo/trunk' doesn't exist - no idea what the Gump-correct URL would be. There are other repositories that are broken as well: xstream, XStream is http://svn.codehaus.org/xstream/trunk The same scheme applies for all Codehaus' projects based on Subversion (Cargo, Groovy). They all changed after the crash of beaver with the availability of the new infrastructure. Basically you can lookup any of them with: http://xircles.codehaus.org/projects/project name/repo javassist, eyebrowse and beanshell. Problem with stable Gump as opposed to trunk Gump is that it doesn't get flagged as a problem, so I usually look at helios to see whether we have problems the repo information. smartfrog was/is in the process of migrating from CVS to svn and I'd consider the current problem transient - read, Steve is going to fix it once the migration is done. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project xstream (in module xstream) failed [EMAIL PROTECTED]: Module directory-naming failed [EMAIL PROTECTED]: Project naming-core (in module directory-naming) failed [EMAIL PROTECTED]: Project naming-factory (in module directory-naming) failed [EMAIL PROTECTED]: Module geronimo failed *** G U M P [EMAIL PROTECTED]: Project xstream (in module xstream) 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 [EMAIL PROTECTED] Project xstream has an issue affecting its community integration. This issue affects 6 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - authx-example : Apache Authentication and Authorization Framework - authx-script : Apache Authentication and Authorization Framework - fulcrum-quartz : Services Framework - groovy : New agile dynamic language using a Java-like syntax for the ... - logging-log4j-chainsaw : Chainsaw log viewer - xstream : simple library to serialize object to XML and back again Full details are available at: http://vmgump.apache.org/gump/public/xstream/xstream/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xstream-10112006.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/xstream/xstream/gump_work/build_xstream_xstream.html Work Name: build_xstream_xstream (Type: Build) Work ended in a state of : Failed Elapsed: 8 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=10112006 [Working Directory: /usr/local/gump/public/workspace/xstream] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/xstream/build/java:/usr/local/gump/public/workspace/xstream/build/test:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-10112006.jar:/usr/local/gump/packages/cglib/cglib-nodep-2.1_3.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/xstream/lib/joda-time-1.2.1.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/jmock/build/dist/jars/jmock-10112006.jar:/usr/local/gump/public/workspace/jmock/build/dist/jars/jmock-cglib-10112006.jar:/usr/local/gump/packages/stax/jsr173_1.0_api.jar:/usr/local/gump/packages/stax/jsr173_1.0_ri.jar:/usr/local/gump/packages/xom-1.1/xom-1.1b3.jar:/usr/local/gump/public/workspace/xpp/build/xpp3-10112006.jar:/usr/local/gump/public/workspace/xstream/lib/xml-writer-0.2.jar - Buildfile: build.xml compile:init: [mkdir] Created dir: /x1/gump/public/workspace/xstream/target/classes [echo] Java version used for compile: 1.5.0_06 compile:java3: [javac] Compiling 200 source files to /x1/gump/public/workspace/xstream/target/classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. compile:java5: [javac] Compiling 8 source files to /x1/gump/public/workspace/xstream/target/classes [javac] Note: /x1/gump/public/workspace/xstream/src/java/com/thoughtworks/xstream/annotations/Annotations.java uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile: benchmark:compile: [mkdir] Created dir: /x1/gump/public/workspace/xstream/target/benchmark-classes BUILD FAILED /x1/gump/public/workspace/xstream/build.xml:65: srcdir
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project xstream (in module xstream) failed [EMAIL PROTECTED]: Module directory-naming failed [EMAIL PROTECTED]: Project naming-core (in module directory-naming) failed [EMAIL PROTECTED]: Project naming-factory (in module directory-naming) failed [EMAIL PROTECTED]: Module geronimo failed *** G U M P [EMAIL PROTECTED]: Project xstream (in module xstream) 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 [EMAIL PROTECTED] Project xstream has an issue affecting its community integration. This issue affects 6 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - authx-example : Apache Authentication and Authorization Framework - authx-script : Apache Authentication and Authorization Framework - fulcrum-quartz : Services Framework - groovy : New agile dynamic language using a Java-like syntax for the ... - logging-log4j-chainsaw : Chainsaw log viewer - xstream : simple library to serialize object to XML and back again Full details are available at: http://vmgump.apache.org/gump/public/xstream/xstream/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xstream-10112006.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/xstream/xstream/gump_work/build_xstream_xstream.html Work Name: build_xstream_xstream (Type: Build) Work ended in a state of : Failed Elapsed: 8 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=10112006 [Working Directory: /usr/local/gump/public/workspace/xstream] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/xstream/build/java:/usr/local/gump/public/workspace/xstream/build/test:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-10112006.jar:/usr/local/gump/packages/cglib/cglib-nodep-2.1_3.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/xstream/lib/joda-time-1.2.1.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/jmock/build/dist/jars/jmock-10112006.jar:/usr/local/gump/public/workspace/jmock/build/dist/jars/jmock-cglib-10112006.jar:/usr/local/gump/packages/stax/jsr173_1.0_api.jar:/usr/local/gump/packages/stax/jsr173_1.0_ri.jar:/usr/local/gump/packages/xom-1.1/xom-1.1b3.jar:/usr/local/gump/public/workspace/xpp/build/xpp3-10112006.jar:/usr/local/gump/public/workspace/xstream/lib/xml-writer-0.2.jar - Buildfile: build.xml compile:init: [mkdir] Created dir: /x1/gump/public/workspace/xstream/target/classes [echo] Java version used for compile: 1.5.0_06 compile:java3: [javac] Compiling 200 source files to /x1/gump/public/workspace/xstream/target/classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. compile:java5: [javac] Compiling 8 source files to /x1/gump/public/workspace/xstream/target/classes [javac] Note: /x1/gump/public/workspace/xstream/src/java/com/thoughtworks/xstream/annotations/Annotations.java uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile: benchmark:compile: [mkdir] Created dir: /x1/gump/public/workspace/xstream/target/benchmark-classes BUILD FAILED /x1/gump/public/workspace/xstream/build.xml:65: srcdir
Re: BATCH: All dressed up, with nowhere to go...
[EMAIL PROTECTED] wrote: Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project xstream (in module xstream) failed [snip] Tried to fix the descriptor... - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 1 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project maven-bootstrap (in module maven) failed *** G U M P [EMAIL PROTECTED]: Project maven-bootstrap (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 [EMAIL PROTECTED] Project maven-bootstrap 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-bootstrap : Project Management Tools Full details are available at: http://vmgump.apache.org/gump/public/maven/maven-bootstrap/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property maven.jar.ant. -DEBUG- Dependency on xml-commons-which exists, no need to add for property maven.jar.which. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/maven/maven-bootstrap/gump_work/build_maven_maven-bootstrap.html Work Name: build_maven_maven-bootstrap (Type: Build) Work ended in a state of : Failed Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dmaven.jar.ant=/usr/local/gump/public/workspace/ant/dist/lib/ant.jar -Dmaven.bootstrap.dir=/usr/local/gump/public/workspace/maven/bootstrap -Dmaven.repo.local=/usr/local/gump/public/workspace/maven/bootstrap/maven.local.repo -Dmaven.bootstrap.classes=/usr/local/gump/public/workspace/maven/bootstrap/bootstrap-classes -Dmaven.jar.commons-logging=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10112006.jar -Dmaven.home=/usr/local/gump/public/workspace/maven/bootstrap/maven.home -Dmaven.home.local=/usr/local/gump/public/workspace/maven/bootstrap/maven.home -Dmaven.jar.commons-cli=/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-10112006.jar -Dmaven.jar.override=true -Dmaven.jar.commons-lang=/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-10112006.jar -Dmaven.jar.commons-httpclient=/usr/local/gump/public/workspace/jakarta-commons/httpclient/dist/commons-httpclient.jar -Dmaven.bootstrap.online=-o -Dmaven.bootstrap.phase1.classes=/usr/local/gump/public/workspace/maven/bootstrap/phase1-classes -Dmaven.jar.velocity=/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-10112006.jar -Dmaven.jar.which=/usr/local/gump/public/workspace/xml-commons/java/build/which.jar -Dmaven.jar.dom4j=/usr/local/gump/public/workspace/dom4j/build/dom4j.jar -f build-bootstrap.xml [Working Directory: /usr/local/gump/public/workspace/maven] CLASSPATH:
