You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Erik Hatcher <er...@ehatchersolutions.com> on 2005/05/08 12:10:29 UTC
Re: [GUMP@brutus]: 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 general@gump.apache.org.
>
> 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 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)
> org/xml/sax/ext/Attributes2
> ---------------------------------------------
>
> To subscribe to this information via syndicated feeds:
> - RSS: http://brutus.apache.org/gump/public/lucene-java/lucene-java/
> rss.xml
> - Atom: http://brutus.apache.org/gump/public/lucene-java/lucene-
> java/atom.xml
>
> ============================== Gump Tracking Only ===
> Produced by Gump version 2.2.
> Gump Run 23000007052005, brutus:brutus-public:23000007052005
> Gump E-mail Identifier (unique within run) #24.
>
> --
> Apache Gump
> http://gump.apache.org/ [Instance: brutus]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java)
failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 10 May 2005, Erik Hatcher <er...@ehatchersolutions.com> wrote:
> 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).
This may be tricky, given the way the task works.
The task checks whether it finds javacc.jar or JavaCC.zip in a
specific location relative to the javacchome attribute. In Gump you
can't trust this alone since Gump will make Ant ignore the internal
classpath of the task.
Given that there really is a lot of convulted logic involved because
the task supports four different versions with three different
classnames and three different archive locations (and no, there is no
one to one mapping of classname to archive location), you are probably
best of creating a condition yourself.
The <available> logic would be something like
<or>
<and>
<!-- JavaCC 1.x or 2.x -->
<or>
<available file="${javacchome}/JavaCC.zip"/>
<available file="${javacchome}/bin/lib/JavaCC.zip"/>
</or>
<available classname="COM.sun.labs.jjdoc.JJDocMain">
<classpath>
<pathelement location="${javacchome}/JavaCC.zip"/>
<pathelement location="${javacchome}/bin/lib/JavaCC.zip"/>
</classpath>
</available>
</and>
<and>
<!-- JavaCC 3.x -->
<or>
<available file="${javacchome}/bin/lib/javacc.jar"/>
<!-- JPackage RPM of 3.x -->
<available file="${javacchome}/javacc.jar"/>
</or>
<or>
<!-- JavaCC 3.0 -->
<available classname="org.netbeans.javacc.jjdoc.JJDocMain">
<classpath>
<pathelement location="${javacchome}/bin/lib/javacc.jar"/>
<pathelement location="${javacchome}/javacc.jar"/>
</classpath>
</available>
<!-- JavaCC 3.1 -->
<available classname="org.javacc.jjdoc.JJDocMain">
<classpath>
<pathelement location="${javacchome}/bin/lib/javacc.jar"/>
<pathelement location="${javacchome}/javacc.jar"/>
</classpath>
</available>
</or>
</and>
</or>
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java)
failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 10 May 2005, Erik Hatcher <er...@ehatchersolutions.com> wrote:
> 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).
This may be tricky, given the way the task works.
The task checks whether it finds javacc.jar or JavaCC.zip in a
specific location relative to the javacchome attribute. In Gump you
can't trust this alone since Gump will make Ant ignore the internal
classpath of the task.
Given that there really is a lot of convulted logic involved because
the task supports four different versions with three different
classnames and three different archive locations (and no, there is no
one to one mapping of classname to archive location), you are probably
best of creating a condition yourself.
The <available> logic would be something like
<or>
<and>
<!-- JavaCC 1.x or 2.x -->
<or>
<available file="${javacchome}/JavaCC.zip"/>
<available file="${javacchome}/bin/lib/JavaCC.zip"/>
</or>
<available classname="COM.sun.labs.jjdoc.JJDocMain">
<classpath>
<pathelement location="${javacchome}/JavaCC.zip"/>
<pathelement location="${javacchome}/bin/lib/JavaCC.zip"/>
</classpath>
</available>
</and>
<and>
<!-- JavaCC 3.x -->
<or>
<available file="${javacchome}/bin/lib/javacc.jar"/>
<!-- JPackage RPM of 3.x -->
<available file="${javacchome}/javacc.jar"/>
</or>
<or>
<!-- JavaCC 3.0 -->
<available classname="org.netbeans.javacc.jjdoc.JJDocMain">
<classpath>
<pathelement location="${javacchome}/bin/lib/javacc.jar"/>
<pathelement location="${javacchome}/javacc.jar"/>
</classpath>
</available>
<!-- JavaCC 3.1 -->
<available classname="org.javacc.jjdoc.JJDocMain">
<classpath>
<pathelement location="${javacchome}/bin/lib/javacc.jar"/>
<pathelement location="${javacchome}/javacc.jar"/>
</classpath>
</available>
</or>
</and>
</or>
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On May 9, 2005, at 9:34 AM, Stefan Bodewig wrote:
> On Mon, 9 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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
> general@gump 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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On May 9, 2005, at 9:34 AM, Stefan Bodewig wrote:
> On Mon, 9 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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
> general@gump 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java)
failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 9 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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
general@gump 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java)
failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 9 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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
general@gump 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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On May 9, 2005, at 3:57 AM, Stefan Bodewig wrote:
> On Sun, 8 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On May 9, 2005, at 3:57 AM, Stefan Bodewig wrote:
> On Sun, 8 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java)
failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 8 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java)
failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 8 May 2005, Erik Hatcher <er...@ehatchersolutions.com> 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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org