Re: [EMAIL PROTECTED]: Project lucene-java (in module lucene-java) failed
Jason or other Gump folks - We'd love to get Lucene's build working fine with Gump. From the error message it doesn't appear this is Lucene-related though. Let me know if there is anything I can do to fix it. I have been refactoring the build process so that all of Lucene's contrib components are also built from the package target. There are some external dependencies that these components need to build properly, and I see that you've got JTidy in there already. The build of contrib/db area requires Berkeley DB's JAR and has a get to download it as part of the build process (though the BDB JAR is not packaged with Lucene). If you don't need javadocs and don't want to deal with any of the external dependencies, run the jar-core target instead of package. Again, let me know if there are changes I can make to help with Gump/ Lucene happiness. Thanks, Erik On May 7, 2005, at 4:29 AM, Jason van Zyl wrote: 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 lucene-java has an issue affecting its community integration. This issue affects 2 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-lucene : Java Based Search Engine - lucene-java : Java Based Search Engine Full details are available at: http://brutus.apache.org/gump/public/lucene-java/lucene-java/ index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [lucene-07052005.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/lucene-java/lucene-java/ gump_work/build_lucene-java_lucene-java.html Work Name: build_lucene-java_lucene-java (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/ local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/ public/gump/work/merge.xml -Dbuild.sysclasspath=only - Dversion=07052005 package [Working Directory: /usr/local/gump/public/workspace/lucene-java] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/ workspace/lucene-java/build/classes/java:/usr/local/gump/public/ workspace/lucene-java/build/classes/demo:/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/dist/junit/junit.jar:/usr/local/ gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/ local/gump/packages/je-1.7.1/lib/je.jar:/usr/local/gump/public/ workspace/jtidy/target/jtidy-07052005.jar - Buildfile: build.xml BUILD FAILED java.lang.NoClassDefFoundError: org/xml/sax/ext/Attributes2 at org.apache.xerces.parsers.AbstractSAXParser.init(Unknown Source) at org.apache.xerces.parsers.SAXParser.init(Unknown Source) at org.apache.xerces.parsers.SAXParser.init(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.init(Unknown Source) at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser (Unknown Source) at org.apache.tools.ant.util.JAXPUtils.newSAXParser (JAXPUtils.java:212) at org.apache.tools.ant.util.JAXPUtils.getNamespaceXMLReader (JAXPUtils.java:169) at org.apache.tools.ant.helper.ProjectHelper2.parse (ProjectHelper2.java:187) at org.apache.tools.ant.helper.ProjectHelper2.parse (ProjectHelper2.java:140) at org.apache.tools.ant.ProjectHelper.configureProject (ProjectHelper.java:90) at org.apache.tools.ant.Main.runBuild(Main.java:653) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:150) at org.apache.tools.ant.Main.main(Main.java:240) Total time: 0 seconds java.lang.NoClassDefFoundError: org/xml/sax/ext/Attributes2 at org.apache.xerces.parsers.AbstractSAXParser.init(Unknown Source) at org.apache.xerces.parsers.SAXParser.init(Unknown Source) at org.apache.xerces.parsers.SAXParser.init(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.init(Unknown Source) at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser (Unknown Source) at
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
On Sun, 8 May 2005, Erik Hatcher [EMAIL PROTECTED] wrote: Jason or other Gump folks - You realize that the mail has been auto-generated and Jason is only the sender because he added the entry and we never bothered to change it, don't you? We'd love to get Lucene's build working fine with Gump. Glad to hear that ;-) From the error message it doesn't appear this is Lucene-related though. Right now we are going through the troubles of Xerces migrating to JAXP 1.3 and xalan doing so as well, but they are doing it with different paces. This makes chosing the correct version of XML APIs a bit difficult. Let me know if there is anything I can do to fix it. Feel free to add any new dependencies Gump is missing. There are some external dependencies that these components need to build properly, and I see that you've got JTidy in there already. The build of contrib/db area requires Berkeley DB's JAR Which I think I've already added as well. and has a get to download it as part of the build process As you probably know, Gump will ignore this. If you don't need javadocs and don't want to deal with any of the external dependencies, run the jar-core target instead of package. This might be an option, thanks. Stefan - 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 13 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module icu4j failed [EMAIL PROTECTED]: Module xdoclet success, but with warnings. [EMAIL PROTECTED]: Module smartfrog success, but with warnings. [EMAIL PROTECTED]: Module db-torque success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project icu4j (in module icu4j) failed [EMAIL PROTECTED]: Project derby-split-1 (in module db-derby) failed [EMAIL PROTECTED]: Project jfor (in module jfor) failed [EMAIL PROTECTED]: Project beepcore (in module beepcore) failed [EMAIL PROTECTED]: Project commons-jci (in module jakarta-commons-sandbox) failed [EMAIL PROTECTED]: Project invicta (in module invicta) failed [EMAIL PROTECTED]: Project JacORB-idllib (in module JacORB) failed *** G U M P [EMAIL PROTECTED]: 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] Module icu4j has an issue affecting its community integration, and has been outstanding for 60 runs. The current state of this module is 'Failed', with reason 'Update Failed'. Full details are available at: http://brutus.apache.org/gump/public/icu4j/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason update failed The following work was performed: http://brutus.apache.org/gump/public/icu4j/gump_work/update_icu4j.html Work Name: update_icu4j (Type: Update) Work ended in a state of : Failed Elapsed: 1 sec Command Line: cvs -q -z3 -d :ext:[EMAIL PROTECTED]:/icu checkout -P -d icu4j icu4j [Working Directory: /usr/local/gump/public/workspace/cvs] - IBM CANADA Ltd. CHS Server D25HTTP004 racky2u15 ** WARNING Access Restricted ** Permission denied (publickey,keyboard-interactive). cvs [checkout aborted]: end of file from server (consult above messages if any) - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/icu4j/rss.xml - Atom: http://brutus.apache.org/gump/public/icu4j/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2409052005, brutus:brutus-public:2409052005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module xdoclet success, but with warnings. 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] Module xdoclet contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/xdoclet/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/xdoclet/gump_work/update_xdoclet.html Work Name: update_xdoclet (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 25 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/xdoclet update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/xdoclet] - cvs [update aborted]: writing to server: Broken pipe - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/xdoclet/rss.xml - Atom: http://brutus.apache.org/gump/public/xdoclet/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2409052005, brutus:brutus-public:2409052005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Module smartfrog success, but with warnings. 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] Module smartfrog contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/smartfrog/index.html That said, some information snippets are provided here. The following annotations
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 13 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module icu4j failed [EMAIL PROTECTED]: Module xdoclet success, but with warnings. [EMAIL PROTECTED]: Module smartfrog success, but with warnings. [EMAIL PROTECTED]: Module db-torque success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project icu4j (in module icu4j) failed [EMAIL PROTECTED]: Project derby-split-1 (in module db-derby) failed [EMAIL PROTECTED]: Project jfor (in module jfor) failed [EMAIL PROTECTED]: Project beepcore (in module beepcore) failed [EMAIL PROTECTED]: Project commons-jci (in module jakarta-commons-sandbox) failed [EMAIL PROTECTED]: Project invicta (in module invicta) failed [EMAIL PROTECTED]: Project JacORB-idllib (in module JacORB) failed *** G U M P [EMAIL PROTECTED]: 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] Module icu4j has an issue affecting its community integration, and has been outstanding for 60 runs. The current state of this module is 'Failed', with reason 'Update Failed'. Full details are available at: http://brutus.apache.org/gump/public/icu4j/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason update failed The following work was performed: http://brutus.apache.org/gump/public/icu4j/gump_work/update_icu4j.html Work Name: update_icu4j (Type: Update) Work ended in a state of : Failed Elapsed: 1 sec Command Line: cvs -q -z3 -d :ext:[EMAIL PROTECTED]:/icu checkout -P -d icu4j icu4j [Working Directory: /usr/local/gump/public/workspace/cvs] - IBM CANADA Ltd. CHS Server D25HTTP004 racky2u15 ** WARNING Access Restricted ** Permission denied (publickey,keyboard-interactive). cvs [checkout aborted]: end of file from server (consult above messages if any) - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/icu4j/rss.xml - Atom: http://brutus.apache.org/gump/public/icu4j/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2409052005, brutus:brutus-public:2409052005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module xdoclet success, but with warnings. 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] Module xdoclet contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/xdoclet/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/xdoclet/gump_work/update_xdoclet.html Work Name: update_xdoclet (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 25 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/xdoclet update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/xdoclet] - cvs [update aborted]: writing to server: Broken pipe - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/xdoclet/rss.xml - Atom: http://brutus.apache.org/gump/public/xdoclet/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2409052005, brutus:brutus-public:2409052005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Module smartfrog success, but with warnings. 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] Module smartfrog contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/smartfrog/index.html That said, some information snippets are provided here. The following annotations
BATCH: Unable to send...
Dear Gumpmeisters, The following 1 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project xalan (in module xml-xalan) failed *** G U M P [EMAIL PROTECTED]: Project xalan (in module xml-xalan) failed Failed with to: [EMAIL PROTECTED] from: [Sam Ruby [EMAIL PROTECTED]] Failed to send notify e-mail: (104, 'Connection reset by peer') 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 xalan has an issue affecting its community integration. This issue affects 322 projects, and has been outstanding for 5 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - addressing : WS-FX Project - anakia : Essentially an XML transformation tool, Anakia uses JDOM and... - ant-embed-optional : Java based build tool - ant-xdocs-proposal : Java based build tool - apacheds-core : Apache Directory Server - apacheds-main : Apache Directory Server - apollo : Apollo Project - apollo-jndi-config : Apollo Project - authx-example : Apache Authentication and Authorization Framework - authx-script : Apache Authentication and Authorization Framework - avalon-http-context : Avalon SVN - avalon-http-demo : Avalon SVN - avalon-http-examples : Avalon SVN - avalon-http-impl : Avalon SVN - avalon-http-server : Avalon SVN - avalon-http-servlet : Avalon SVN - avalon-http-static : Avalon SVN - avalon-http-test : Avalon SVN - avalon-jmx-mx4j : Avalon SVN - avalon-jmx-spi : Avalon SVN - avalon-jmx-test : Avalon SVN - avalon-jmx-util : Avalon SVN - avalon-planet-facilities : Avalon SVN - avalon-tutorial-webserver : Avalon SVN - bsh - cargo : Cargo provides a Java API to manipulate Java Containers - cddlm : Configuration and Deployment of Grid Applications and System... - checkstyle : Java style checker - checkstyle-test : Java style checker - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-feedparser : Generic FeedParser interface and concrete implementation... - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-antlr : Commons Jelly - commons-jelly-tags-avalon : Commons Jelly - commons-jelly-tags-bean : Commons Jelly - commons-jelly-tags-beanshell : Commons Jelly - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-bsf : Commons Jelly - commons-jelly-tags-define : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-html : Commons Jelly -
BATCH: Unable to send...
Dear Gumpmeisters, The following 1 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project xalan (in module xml-xalan) failed *** G U M P [EMAIL PROTECTED]: Project xalan (in module xml-xalan) failed Failed with to: [EMAIL PROTECTED] from: [Sam Ruby [EMAIL PROTECTED]] Failed to send notify e-mail: (104, 'Connection reset by peer') 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 xalan has an issue affecting its community integration. This issue affects 322 projects, and has been outstanding for 5 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - addressing : WS-FX Project - anakia : Essentially an XML transformation tool, Anakia uses JDOM and... - ant-embed-optional : Java based build tool - ant-xdocs-proposal : Java based build tool - apacheds-core : Apache Directory Server - apacheds-main : Apache Directory Server - apollo : Apollo Project - apollo-jndi-config : Apollo Project - authx-example : Apache Authentication and Authorization Framework - authx-script : Apache Authentication and Authorization Framework - avalon-http-context : Avalon SVN - avalon-http-demo : Avalon SVN - avalon-http-examples : Avalon SVN - avalon-http-impl : Avalon SVN - avalon-http-server : Avalon SVN - avalon-http-servlet : Avalon SVN - avalon-http-static : Avalon SVN - avalon-http-test : Avalon SVN - avalon-jmx-mx4j : Avalon SVN - avalon-jmx-spi : Avalon SVN - avalon-jmx-test : Avalon SVN - avalon-jmx-util : Avalon SVN - avalon-planet-facilities : Avalon SVN - avalon-tutorial-webserver : Avalon SVN - bsh - cargo : Cargo provides a Java API to manipulate Java Containers - cddlm : Configuration and Deployment of Grid Applications and System... - checkstyle : Java style checker - checkstyle-test : Java style checker - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-feedparser : Generic FeedParser interface and concrete implementation... - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-antlr : Commons Jelly - commons-jelly-tags-avalon : Commons Jelly - commons-jelly-tags-bean : Commons Jelly - commons-jelly-tags-beanshell : Commons Jelly - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-bsf : Commons Jelly - commons-jelly-tags-define : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-html : Commons Jelly -
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
On May 9, 2005, at 3:57 AM, Stefan Bodewig wrote: On Sun, 8 May 2005, Erik Hatcher [EMAIL PROTECTED] wrote: Jason or other Gump folks - You realize that the mail has been auto-generated and Jason is only the sender because he added the entry and we never bothered to change it, don't you? I figured if his address is on the e-mail then replying to it is fair game :) But I made sure to reply to the gump list also. From the error message it doesn't appear this is Lucene-related though. Right now we are going through the troubles of Xerces migrating to JAXP 1.3 and xalan doing so as well, but they are doing it with different paces. This makes chosing the correct version of XML APIs a bit difficult. I'll stay tuned for when this settles down and any build failures are truly Lucene build failures and not Gump environment related. Let me know if there is anything I can do to fix it. Feel free to add any new dependencies Gump is missing. What's the process for me to add new dependencies? I should also tweak the build so that it has conditional build aspects to it and doesn't try to build the code related to Berkeley DB if the classes are not present. There are some external dependencies that these components need to build properly, and I see that you've got JTidy in there already. The build of contrib/db area requires Berkeley DB's JAR Which I think I've already added as well. Excellent. and has a get to download it as part of the build process As you probably know, Gump will ignore this. Just out of curiosity, how does it ignore get? If you don't need javadocs and don't want to deal with any of the external dependencies, run the jar-core target instead of package. This might be an option, thanks. It's possible other projects would depend on the contrib libraries like the Highlighter and Spell Checker, so it'd be best to let package run fully if possible. Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
On Mon, 9 May 2005, Erik Hatcher [EMAIL PROTECTED] wrote: On May 9, 2005, at 3:57 AM, Stefan Bodewig wrote: Feel free to add any new dependencies Gump is missing. What's the process for me to add new dependencies? If the project you depend on is already known to Gump: * check out gump/projects/lucene-java.xml from CVS. * modify it (by adding a depend tag, you will understand how when you look into the descriptor). * commit it - yes, you can, every ASF committer can. If it a new project, i.e. something Gump doesn't build yet, you can either read about Gump descriptors on our homepage or come to [EMAIL PROTECTED] and ask for help. and has a get to download it as part of the build process As you probably know, Gump will ignore this. Just out of curiosity, how does it ignore get? It doesn't ignore the get, it ignores your classpath settings. build.sysclasspath=only is the key. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem running Apache Gump [brutus-public]
There is a problem with run 'brutus-public' (09052005_180001), location : http://brutus.apache.org/gump/public The log ought be at: http://brutus.apache.org/gump/public/gump_log.txt The last (up to) 50 lines of the log are : dynagumper.py processModule: need to implement module event processing Perform Update on #[(47, 247)] : jakarta-tomcat-jasper_tc4 Perform Update on #[(48, 247)] : packaged-strutstestcase Perform Update on #[(49, 247)] : nanocontainer dynagumper.py processModule: need to implement module event processing Perform Update on #[(50, 247)] : ognl dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(51, 247)] : packaged-jetty Perform Update on #[(52, 247)] : jakarta-tomcat-connectors dynagumper.py processModule: need to implement module event processing Perform Update on #[(53, 247)] : eclipse dynagumper.py processModule: need to implement module event processing Perform Update on #[(54, 247)] : bouncycastle dynagumper.py processModule: need to implement module event processing Perform Update on #[(55, 247)] : bdb-je Perform Update on #[(56, 247)] : beepcore dynagumper.py processModule: need to implement module event processing Perform Update on #[(57, 247)] : excalibur-legacy Perform Update on #[(58, 247)] : jakarta-slide Perform Update on #[(59, 247)] : j2ee-connector Perform Update on #[(60, 247)] : jcifs dynagumper.py processModule: need to implement module event processing Perform Update on #[(61, 247)] : d-haven Perform Update on #[(62, 247)] : jisp dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(63, 247)] : saxon7 dynagumper.py processModule: need to implement module event processing Perform Update on #[(64, 247)] : packaged-jaxen dynagumper.py processModule: need to implement module event processing Perform Update on #[(65, 247)] : jakarta-commons-codec-11 dynagumper.py processModule: need to implement module event processing Perform Update on #[(66, 247)] : janino dynagumper.py processModule: need to implement module event processing Perform Update on #[(67, 247)] : forehead dynagumper.py processModule: need to implement module event processing Perform Update on #[(68, 247)] : nsuml dynagumper.py processModule: need to implement module event processing Perform Update on #[(69, 247)] : db-ojb Perform Update on #[(70, 247)] : jetty4 dynagumper.py processModule: need to implement module event processing Perform Update on #[(71, 247)] : iso-relax dynagumper.py processModule: need to implement module event processing Perform Update on #[(72, 247)] : jakarta-commons-sandbox Perform SVN Update on #[(72, 247)] : jakarta-commons-sandbox Perform Update on #[(73, 247)] : ibatis Process Exit Code : 139 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem running Apache Gump [brutus-public]
There is a problem with run 'brutus-public' (09052005_180001), location : http://brutus.apache.org/gump/public The log ought be at: http://brutus.apache.org/gump/public/gump_log.txt The last (up to) 50 lines of the log are : dynagumper.py processModule: need to implement module event processing Perform Update on #[(47, 247)] : jakarta-tomcat-jasper_tc4 Perform Update on #[(48, 247)] : packaged-strutstestcase Perform Update on #[(49, 247)] : nanocontainer dynagumper.py processModule: need to implement module event processing Perform Update on #[(50, 247)] : ognl dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(51, 247)] : packaged-jetty Perform Update on #[(52, 247)] : jakarta-tomcat-connectors dynagumper.py processModule: need to implement module event processing Perform Update on #[(53, 247)] : eclipse dynagumper.py processModule: need to implement module event processing Perform Update on #[(54, 247)] : bouncycastle dynagumper.py processModule: need to implement module event processing Perform Update on #[(55, 247)] : bdb-je Perform Update on #[(56, 247)] : beepcore dynagumper.py processModule: need to implement module event processing Perform Update on #[(57, 247)] : excalibur-legacy Perform Update on #[(58, 247)] : jakarta-slide Perform Update on #[(59, 247)] : j2ee-connector Perform Update on #[(60, 247)] : jcifs dynagumper.py processModule: need to implement module event processing Perform Update on #[(61, 247)] : d-haven Perform Update on #[(62, 247)] : jisp dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(63, 247)] : saxon7 dynagumper.py processModule: need to implement module event processing Perform Update on #[(64, 247)] : packaged-jaxen dynagumper.py processModule: need to implement module event processing Perform Update on #[(65, 247)] : jakarta-commons-codec-11 dynagumper.py processModule: need to implement module event processing Perform Update on #[(66, 247)] : janino dynagumper.py processModule: need to implement module event processing Perform Update on #[(67, 247)] : forehead dynagumper.py processModule: need to implement module event processing Perform Update on #[(68, 247)] : nsuml dynagumper.py processModule: need to implement module event processing Perform Update on #[(69, 247)] : db-ojb Perform Update on #[(70, 247)] : jetty4 dynagumper.py processModule: need to implement module event processing Perform Update on #[(71, 247)] : iso-relax dynagumper.py processModule: need to implement module event processing Perform Update on #[(72, 247)] : jakarta-commons-sandbox Perform SVN Update on #[(72, 247)] : jakarta-commons-sandbox Perform Update on #[(73, 247)] : ibatis Process Exit Code : 139 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
