Re: [EMAIL PROTECTED]: Project lucene-java (in module lucene-java) failed
What is going wrong with the Gump Lucene build? It is missing JUnit
- but this is something Gump itself should provide somehow, correct?
Please reply back to java-dev@lucene.apache.org if you have some
insight into this and it is something the Lucene team can address.
Thanks,
Erik
On Feb 16, 2006, at 4:26 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,
and has been outstanding for 197 runs.
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://vmgump.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-core-16022006.jar] identifier set to
project name
-DEBUG- Dependency on javacc exists, no need to add for property
javacc.home.
-INFO- Failed with reason build failed
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.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: 20 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 -
Dversion=16022006 -Djavacc.home=/usr/local/gump/packages/javacc-3.1
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:junit-gump-15022006.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/packages/javacc-3.1/bin/lib/
javacc.jar:/usr/local/gump/public/workspace/httpunit/jars/Tidy.jar
-
[javac] location: class
org.apache.lucene.queryParser.TestMultiFieldQueryParser
[javac] public class TestMultiFieldQueryParser extends TestCase {
[javac]^
[javac] /x1/gump/public/workspace/lucene-java/src/test/org/
apache/lucene/queryParser/TestQueryParser.java:19: package
junit.framework does not exist
[javac] import junit.framework.TestCase;
[javac]^
[javac] /x1/gump/public/workspace/lucene-java/src/test/org/
apache/lucene/queryParser/TestQueryParser.java:53: cannot resolve
symbol
[javac] symbol : class TestCase
[javac] location: class
org.apache.lucene.queryParser.TestQueryParser
[javac] public class TestQueryParser extends TestCase {
[javac] ^
[javac] /x1/gump/public/workspace/lucene-java/src/test/org/
apache/lucene/search/BaseTestRangeFilter.java:21: package
junit.framework does not exist
[javac] import junit.framework.TestCase;
[javac]^
[javac] /x1/gump/public/workspace/lucene-java/src/test/org/
apache/lucene/search/BaseTestRangeFilter.java:29: cannot resolve
symbol
[javac] symbol : class TestCase
[javac] location: class
org.apache.lucene.search.BaseTestRangeFilter
[javac] public class BaseTestRangeFilter extends TestCase {
[javac] ^
[javac] /x1/gump/public/workspace/lucene-java/src/test/org/
apache/lucene/search/CheckHits.java:19: package junit.framework
does not exist
[javac] import junit.framework.TestCase;
[javac]^
[javac] /x1/gump/public/workspace/lucene-java/src/test/org/
apache/lucene/search/QueryUtils.java:3: package junit.framework
does not exist
[javac] import junit.framework.TestCase;
Re: Gump3 Presentation -- choice of technology
On Jun 30, 2005, at 7:24 PM, Adam R. B. Jack wrote: To my knowledge here are the best known candiates (plus some others I've heard discussed.) - Java JSP/Struts. - Cocoon (Stefano has spent significant time on this, he feels it is worth evaluating.) - mod_python (Leo has spent some time on this, he feels it is worth evaluating.) - PHP (why not?) To toss another idea out there... I highly recommend Ruby on Rails - it's elegant, clean, and ties to a DB easily. Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
Gumpers, What is the issue with Lucene building with Gump? To me it looks as if its not doing a clean build and thus cannot find the JAR that was successfully built in a past run because its looking for it by a different dated name. What does it take to get a clean build going? Should that be part of the target that Gump runs to clean out past build artifacts? Or should it be Gump itself that cleans the slate? Thanks, Erik Begin forwarded message: From: Jason van Zyl [EMAIL PROTECTED] Date: May 15, 2005 5:12:52 AM EDT To: lucene-dev@jakarta.apache.org Subject: [EMAIL PROTECTED]: Project lucene-java (in module lucene-java) failed Reply-To: java-dev@lucene.apache.org 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 3 projects, and has been outstanding for 16 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - eyebrowse : Web-based mail archive browsing - 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-15052005.jar] identifier set to project name -DEBUG- Dependency on javacc exists, no need to add for property javacc.home. -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/lucene- java/build/lucene-15052005.jar -ERROR- See Directory Listing Work for Missing Outputs -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 : Success Elapsed: 27 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/java/build/ xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/ workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only - Dversion=15052005 -Djavacc.home=/usr/local/gump/packages/javacc-3.1 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/packages/ javacc-3.1/bin/lib/javacc.jar:/usr/local/gump/public/workspace/ jtidy/target/jtidy-15052005.jar - default: [echo] Building swing... javacc-uptodate-check: javacc-notice: common.init: build-lucene: init: compile-core: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/ lucene-java/build/contrib/swing/classes/java [javac] Compiling 2 source files to /home/gump/workspaces2/ public/workspace/lucene-java/build/contrib/swing/classes/java [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. jar-core: [jar] Building jar: /home/gump/workspaces2/public/workspace/ lucene-java/build/contrib/swing/lucene-swing-15052005.jar default: [echo] Building wordnet... javacc-uptodate-check: javacc-notice: common.init: build-lucene: init: compile-core: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/ lucene-java/build/contrib/wordnet/classes/java [javac] Compiling 3 source files to /home/gump/workspaces2/ public/workspace/lucene-java/build/contrib/wordnet/classes/java jar-core: [jar] Building jar: /home/gump/workspaces2/public/workspace/ lucene-java/build/contrib/wordnet/lucene-wordnet-15052005.jar default: package: [mkdir] Created dir: /home/gump/workspaces2/public/workspace/ lucene-java/dist BUILD
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
On May 9, 2005, at 9:34 AM, Stefan Bodewig wrote: 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. Stefan - thanks! I have, as you probably have seen, just committed a cosmetic change to the lucene-java.xml file while troubleshooting the latest failure caused by the missing JavaCC and saw that you had already taken care of it. JavaCC is not strictly required to build Lucene, as we commit the generated files, but in my refactorings I made it necessary, not necessarily intentionally. I can (and probably will) change it such that jjdoc is not run if JavaCC is not present and adjust it so that the check for JavaCC is only done on the targets that truly need it (but are not part of the main build path). I'm now attentively tuned in to the Lucene Gump failures, and will jump in to help if needed. Hopefully the JavaCC adjustment you made is all that is needed to make Gump happy. Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 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]
