RE: excalibur-configuration
Niclas, Looks like you got fulcrum-crypto-impl to build! Congratulations, that was one of the bugaboo projects because of the Javamail dependency. Thanks for fixing up all those other dependencies as well! Eric -Original Message- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 6:14 AM To: Gump code and data Subject: Re: excalibur-configuration Niclas Hedhman wrote: Excalibur gang, Jakarta Turbine Fulcrum has a couple of projects that depends on the excalibur-configuration project, which doesn't exist anymore. What is the migration path for this artifact? project name=excalibur-legacy jar name=excalibur-compatibility-1.1.jar id=compatibility/ jar name=excalibur-i18n-1.1.jar id=i18n/ jar name=excalibur-configuration-1.2.jar id=configuration/ /project found in module project/excalibur-legacy. Grep is your friend :-) -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Kaffe instance and ant-bootstrap
On Wed, 27 Oct 2004, Niclas Hedhman [EMAIL PROTECTED] wrote: I have looked at the Kaffe instance and its inability to create the Ant bootstrap. The first level of problem is that the Kaffe compiler doesn't imply any source files that are not specified, and that results in the immense number of Cannot find class. I think the only viable solution is to drop kopi and use jikes as a compiler. The very same problem is likely to come up in javac tasks later on as well. There already is an issue in Jira for this. Ant's bootstrap script can use jikes easily by setting the JAVAC environment variable. I don't know if we should proceed by convincing Ant to introduce this to their codebase, or we should maintain a separate bootstrap script. I'd prefer to really not use kopi at all. I've been told that even the Kaffe people prefer to use Jikes. Any approach like yours will need to be maintained when classes get added to Ant. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: excalibur-configuration
I am not sure how we depend on it.. It seems like things just fail if we don't have it... -Original Message- From: peter royal [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 4:47 AM To: Excalibur Developers List Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: excalibur-configuration On Oct 26, 2004, at 10:18 PM, Niclas Hedhman wrote: Excalibur gang, Jakarta Turbine Fulcrum has a couple of projects that depends on the excalibur-configuration project, which doesn't exist anymore. What is the migration path for this artifact? What aspects do they depend on? if they are the only dependees, might sense for them to pull the code into their codebase? -pete - 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]
Gump Versions
Hi, I'm relatively new to gump but have up until now been running the latest version of gump from the svn repository. One of the first things that happens when Gump runs is that it gets the latest version of itself from svn. A couple of nights ago the gump version went from 2.1.0-alpha-003 to 2.2 at which point the build stopped working with the error message :- Traceback (most recent call last): File gump.py, line 118, in ? main(sys.argv) File gump.py, line 108, in main getattr(command, process)(options,arguments) File /src/external/cvs/gump/python/gump/commands/build.py, line 41, in process workspace = WorkspaceLoader(options.isCache()).load(ws) AttributeError: 'list' object has no attribute 'isCache' I have since seen on the Wiki that there is a separate branch (gump-live) which I have now checked out. The version in here though is 2.02-alpha-0003. Also I notice that the build run on Brutus is still using the 2.1.0-alpha-0003 version. How do I set up gump to run with the same version as Brutus and not update itself during the build? Thanks Gareth Webbley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump Versions
Gareth Webbley wrote: Hi, I'm relatively new to gump but have up until now been running the latest version of gump from the svn repository. One of the first things that happens when Gump runs is that it gets the latest version of itself from svn. A couple of nights ago the gump version went from 2.1.0-alpha-003 to 2.2 at which point the build stopped working with the error message :- Traceback (most recent call last): File gump.py, line 118, in ? main(sys.argv) File gump.py, line 108, in main getattr(command, process)(options,arguments) File /src/external/cvs/gump/python/gump/commands/build.py, line 41, in process workspace = WorkspaceLoader(options.isCache()).load(ws) AttributeError: 'list' object has no attribute 'isCache' The 'trunk' (aka 2.2 today) is not ready to go and should be considered alpha. I have since seen on the Wiki that there is a separate branch (gump-live) which I have now checked out. This is the version that runs on brutus. The version in here though is 2.02-alpha-0003. Also I notice that the build run on Brutus is still using the 2.1.0-alpha-0003 version. I think that's because you run it from gump.py instead of running it from cron/gump.sh How do I set up gump to run with the same version as Brutus and not update itself during the build? checkout the live branch and run it from cron/gump.sh sorry for the mess, I'm working to make things easier with a single (and hopefully well commented) entry point. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 4 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project dumpster (in module dumpster) failed [EMAIL PROTECTED]: Project icu4j (in module icu4j) failed [EMAIL PROTECTED]: Project excalibur-pool (in module excalibur) success [EMAIL PROTECTED]: Project excalibur-thread (in module excalibur) success *** G U M P [EMAIL PROTECTED]: Project dumpster (in module dumpster) 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 dumpster 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: - dumpster : The Dumbster is a very simple fake SMTP server designed for ... Full details are available at: http://brutus.apache.org/gump/public/dumpster/dumpster/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [dumbster.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://brutus.apache.org/gump/public/dumpster/dumpster/gump_work/build_dumpster_dumpster.html Work Name: build_dumpster_dumpster (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only world [Working Directory: /usr/local/gump/public/workspace/dumpster] CLASSPATH : /opt/jdk1.4/lib/tools.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar:/usr/local/gump/packages/javamail-1.3/lib/mailapi.jar - Exception in thread main java.lang.NoClassDefFoundError: org/apache/tools/ant/Main - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/dumpster/dumpster/rss.xml - Atom: http://brutus.apache.org/gump/public/dumpster/dumpster/atom.xml == Gump Tracking Only === Produced by Gump version 2.1.0-alpha-0003. Gump Run 18000327102004, brutus:brutus-public:18000327102004 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Project icu4j (in module icu4j) 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 icu4j 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: - icu4j : UDDI client Full details are available at: http://brutus.apache.org/gump/public/icu4j/icu4j/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [icu4j.jar] identifier set to project name -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/icu4j/icu4j/gump_work/build_icu4j_icu4j.html Work Name: build_icu4j_icu4j (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only all [Working Directory: /usr/local/gump/public/workspace/icu4j] CLASSPATH : /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/icu4j/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/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-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 - core: [javac]
Re: Gump Versions
Thanks Stefano, I'll give that a try. Gareth On Wednesday 27 October 2004 14:07, Stefano Mazzocchi wrote: Gareth Webbley wrote: Hi, I'm relatively new to gump but have up until now been running the latest version of gump from the svn repository. One of the first things that happens when Gump runs is that it gets the latest version of itself from svn. A couple of nights ago the gump version went from 2.1.0-alpha-003 to 2.2 at which point the build stopped working with the error message :- Traceback (most recent call last): File gump.py, line 118, in ? main(sys.argv) File gump.py, line 108, in main getattr(command, process)(options,arguments) File /src/external/cvs/gump/python/gump/commands/build.py, line 41, in process workspace = WorkspaceLoader(options.isCache()).load(ws) AttributeError: 'list' object has no attribute 'isCache' The 'trunk' (aka 2.2 today) is not ready to go and should be considered alpha. I have since seen on the Wiki that there is a separate branch (gump-live) which I have now checked out. This is the version that runs on brutus. The version in here though is 2.02-alpha-0003. Also I notice that the build run on Brutus is still using the 2.1.0-alpha-0003 version. I think that's because you run it from gump.py instead of running it from cron/gump.sh How do I set up gump to run with the same version as Brutus and not update itself during the build? checkout the live branch and run it from cron/gump.sh sorry for the mess, I'm working to make things easier with a single (and hopefully well commented) entry point. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Copy junit reports doesn't work...
Python-masters, Look at the content in the directory ~/workspaces/public/results/cocoon/cocoon/gump_file on brutus. There are two things that are not right; 1. Everything has an additional .html to it. 2. Directories are not copied recursively. Apparently there is an attemp somewhere to copy the junit results to a browsable output area, which is great now when we will be hitting more and more testcase failures, and quickly provide the output to the people it concerns. Since it is almost in place, can someone have a quick look at it, and see if there is a quick fix. Cheers Niclas P.S. I have been aimlessly looking at heaps of Python code, and the only copying I can find is in python/gump/util/sync.py, and that looks Ok to me. And the only place where html seems to be added to the mix is in the python/gump/actor/document/xdocs/ package, which I would guess shouldn't be involved in this... -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
On 27 Oct 2004, [EMAIL PROTECTED] wrote: Adding the xmlParserAPIs for some Maven projects in Fulcrum. + project name=xmlParserAPIspackage=jetty-5.0.RC4/ Isn't this the same jar that we created during the Xerces build? The 2.5 in the jar name in Jetty suggests Xerces-J 2.5 to me. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
On Wednesday 27 October 2004 23:46, Stefan Bodewig wrote: On 27 Oct 2004, [EMAIL PROTECTED] wrote: Adding the xmlParserAPIs for some Maven projects in Fulcrum. + project name=xmlParserAPIspackage=jetty-5.0.RC4/ Isn't this the same jar that we created during the Xerces build? The 2.5 in the jar name in Jetty suggests Xerces-J 2.5 to me. Perhaps. Feel free to try to get the name xmlParserAPIs to map against the Maven artifactID of the same name. ATM, type=boot jars will not map to Maven jar overrides, and I couldn't figure out any other way to handle this. Cheers Niclas -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem running Apache Gump...
There is a problem with the run at : http://brutus.apache.org/gump/public The log ought be at: http://brutus.apache.org/gump/public/gump_log_27102004_090001.txt The last (up to) 50 lines of the log are : INFO:gump:Update(s) received via on #[(153, 197)] : excalibur INFO:gump:Perform Update on #[(168, 197)] : quartz INFO:gump:Update(s) received via CVS on #[(168, 197)] : quartz INFO:gump:Update(s) received via on #[(168, 197)] : quartz INFO:gump:Perform Update on #[(169, 197)] : xml-fop-maintenance INFO:gump:Update(s) received via on #[(162, 197)] : xml-xmlbeans INFO:gump:Perform Update on #[(170, 197)] : jelly-tags INFO:gump:Perform Update on #[(171, 197)] : uddi4j INFO:gump:Perform Update on #[(172, 197)] : struts-sslext INFO:gump:Update(s) received via on #[(172, 197)] : struts-sslext INFO:gump:Perform Update on #[(173, 197)] : maven INFO:gump:Update(s) received via on #[(165, 197)] : struts INFO:gump:Perform Update on #[(174, 197)] : ws-wsif INFO:gump:Perform Update on #[(175, 197)] : jakarta-bsf INFO:gump:Perform Update on #[(176, 197)] : beanshell INFO:gump:Perform Update on #[(177, 197)] : mx4j INFO:gump:Update(s) received via on #[(176, 197)] : beanshell INFO:gump:Perform Update on #[(178, 197)] : jgroups INFO:gump:Perform Update on #[(179, 197)] : directory-naming INFO:gump:Perform SVN Update on #[(179, 197)] : directory-naming INFO:gump:Perform Update on #[(180, 197)] : incubator-geronimo INFO:gump:Update(s) received via CVS on #[(166, 197)] : ws-axis INFO:gump:Perform Update on #[(181, 197)] : jakarta-velocity-tools INFO:gump:Perform Update on #[(182, 197)] : ws-juddi INFO:gump:Update(s) received via on #[(177, 197)] : mx4j INFO:gump:Perform Update on #[(183, 197)] : ws-wsil INFO:gump:Perform Update on #[(184, 197)] : javagroups INFO:gump:Update(s) received via on #[(181, 197)] : jakarta-velocity-tools INFO:gump:Perform Update on #[(185, 197)] : jetty INFO:gump:Perform Update on #[(186, 197)] : jakarta-tomcat INFO:gump:Perform Update on #[(187, 197)] : xml-fop INFO:gump:Perform Update on #[(188, 197)] : jakarta-tomcat-catalina INFO:gump:Update(s) received via CVS on #[(188, 197)] : jakarta-tomcat-catalina INFO:gump:Perform Update on #[(189, 197)] : wss4j INFO:gump:Perform Update on #[(190, 197)] : jakarta-turbine-jcs INFO:gump:Perform Update on #[(191, 197)] : jakarta-jmeter-20 INFO:gump:Update(s) received via on #[(188, 197)] : jakarta-tomcat-catalina INFO:gump:Perform Update on #[(192, 197)] : jakarta-turbine-3 INFO:gump:Perform Update on #[(193, 197)] : jakarta-turbine-2 INFO:gump:Perform Update on #[(194, 197)] : jakarta-jetspeed INFO:gump:Perform Update on #[(195, 197)] : scarab INFO:gump:Perform Update on #[(196, 197)] : lenya INFO:gump:Perform SVN Update on #[(196, 197)] : lenya INFO:gump:Update(s) received via on #[(191, 197)] : jakarta-jmeter-20 INFO:gump:Perform Update on #[(197, 197)] : commons-vfs INFO:gump:Update(s) received via CVS on #[(194, 197)] : jakarta-jetspeed INFO:gump:Update(s) received via CVS on #[(195, 197)] : scarab INFO:gump:Update(s) received via on #[(166, 197)] : ws-axis INFO:gump:Update(s) received via on #[(195, 197)] : scarab Process Exit Code : 1 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
Niclas Hedhman wrote: Stefan Bodewig wrote: Niclas Hedman wrote: Adding the xmlParserAPIs for some Maven projects in Fulcrum. + project name=xmlParserAPIspackage=jetty-5.0.RC4/ Isn't this the same jar that we created during the Xerces build? The 2.5 in the jar name in Jetty suggests Xerces-J 2.5 to me. Perhaps. Feel free to try to get the name xmlParserAPIs to map against the Maven artifactID of the same name. ATM, type=boot jars will not map to Maven jar overrides, and I couldn't figure out any other way to handle this. Is this the same xml-apis that are provided by Apache XML Commons? -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
