I've modified your Gump descriptor to use the downloaded version of the jar.
However, this prevents you from getting warnings if that project makes
imcompatible changes that would break your project. It would be better to
set up that project to build under Gump, and then depend / on it in your
Greetings Gumpers,
The Lucene-Java gump build seems to been failing consistently for the past
few days. The problem seems to relate to some cleanup we did recently to
our build files to help ensure that the various contrib sub projects
could be cleanly built/tested on their own, or as part of
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,
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 16, 2006 12:09 PM
To: java-dev@lucene.apache.org
Cc: Gump code and data
Subject: Re: [EMAIL PROTECTED]: Project lucene-java (in module
lucene-java) failed
What is going wrong
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
