Build failed in Hudson: Lucene-Nightly #151
See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/151/changes -- [...truncated 829 lines...] AUcontrib/gdata-server/lib/commons-logging-1.1.jar AUcontrib/gdata-server/lib/commons-beanutils.jar AUcontrib/gdata-server/lib/log4j-1.2.13.jar AUcontrib/gdata-server/lib/nekohtml.jar AUcontrib/gdata-server/lib/commons-digester-1.7.jar A contrib/gdata-server/src A contrib/gdata-server/src/gom A contrib/gdata-server/src/gom/src A contrib/gdata-server/src/gom/src/test A contrib/gdata-server/src/gom/src/test/org A contrib/gdata-server/src/gom/src/test/org/apache A contrib/gdata-server/src/gom/src/test/org/apache/lucene A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/GOMNamespaceTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMContentImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMDocumentImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMDateConstructImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMTextConstructImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMGenereatorImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMCategoryTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMIdImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMLinkImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/ArbitraryGOMXmlTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMSourceImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMEntryImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMAuthorImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMFeedImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMAttributeImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/SimpleGOMElementImplTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/AtomUriElementTest.java A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMPersonImplTest.java A contrib/gdata-server/src/gom/src/java A contrib/gdata-server/src/gom/src/java/org A contrib/gdata-server/src/gom/src/java/org/apache A contrib/gdata-server/src/gom/src/java/org/apache/lucene A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMXmlEntity.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMSummary.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMLink.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMTime.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMLogo.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMAuthor.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMAttribute.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/GOMFeed.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMContributorImpl.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/core-aid.uml A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMDocumentImpl.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMPublishedImpl.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMDateConstructImpl.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMFactory.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMGeneratorImpl.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/GOMIconImpl.java A contrib/gdata-server/src/gom/src/java/org/apache/lucene/gdata/gom/core/SimpleE
[jira] Updated: (LUCENE-713) File Formats Documentation is not correct for Term Vectors
[ https://issues.apache.org/jira/browse/LUCENE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shahan Khatchadourian updated LUCENE-713: - In the current implementation, token offsets are not stored as they are provided in the Token. DocumentWriter makes a token's startOffset relative to +1 of the previous Token's endOffset. > File Formats Documentation is not correct for Term Vectors > -- > > Key: LUCENE-713 > URL: https://issues.apache.org/jira/browse/LUCENE-713 > Project: Lucene - Java > Issue Type: Bug > Components: Website >Reporter: Grant Ingersoll >Assignee: Grant Ingersoll >Priority: Minor > > From Samir Abdou on the dev mailing list: > Hi, > There is an inconsistency between the files format page (from Lucene > website) and the source code. It concerns the positions and offsets of term > vectors. It seems that documentation (website) is not up to date. According > to the file format page, offsets and positions are not stored! Is that > correct? > Many thanks, > Samir > - > Indeed, in the file formats term vectors section it doesn't talk about the > storing of position and offset info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-579) TermPositionVector offsets incorrect if indexed field has multiple values and one ends with non-term chars
[
https://issues.apache.org/jira/browse/LUCENE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512743
]
Shahan Khatchadourian commented on LUCENE-579:
--
DocumentWriter seems to be the culprit in adding 1 to the previous token's
endOffset. It may not be possible to provide token offsets that "undo" this
operation since it is not possible to determine the order in which tokens are
handled as they are grouped by field which doesn't necessarily correspond to
document-order. This would also interfere with custom synonym tokens since
custom token offsets are no longer guaranteed.
I suggest that there be a flag in Fieldable or IndexWriter which allows exact
provided offsets to be stored rather than increased by one. There does not seem
to be any sanity checks on offset values during reading/writing the term vector.
A current workaround to this issue is to store the correct startOffset, but
leave the endOffset as -1. This has the effect of undoing the +1 of the
previous token's endOffset but prevents endOffset information from being
available without retokenizing/reparsing the original document.
> TermPositionVector offsets incorrect if indexed field has multiple values and
> one ends with non-term chars
> --
>
> Key: LUCENE-579
> URL: https://issues.apache.org/jira/browse/LUCENE-579
> Project: Lucene - Java
> Issue Type: Bug
> Components: Analysis
>Affects Versions: 1.9
>Reporter: Keiron McCammon
>
> If you add multiple values for a field with term vector positions and offsets
> enabled and one of the values ends with a non-term then the offsets for the
> terms from subsequent values are wrong. For example (note the '.' in the
> first value):
> IndexWriter writer = new IndexWriter(directory, new SimpleAnalyzer(),
> true);
> Document doc = new Document();
> doc.add(new Field("", "one.", Field.Store.YES, Field.Index.TOKENIZED,
> Field.TermVector.WITH_POSITIONS_OFFSETS));
> doc.add(new Field("", "two", Field.Store.YES, Field.Index.TOKENIZED,
> Field.TermVector.WITH_POSITIONS_OFFSETS));
> writer.addDocument(doc);
> writer.optimize();
> writer.close();
> IndexSearcher searcher = new IndexSearcher(directory);
> Hits hits = searcher.search(new MatchAllDocsQuery());
> Highlighter highlighter = new Highlighter(new SimpleHTMLFormatter(),
> new QueryScorer(new TermQuery(new Term("", "camera")),
> searcher.getIndexReader(), ""));
> for (int i = 0; i < hits.length(); ++i) {
> TermPositionVector v = (TermPositionVector)
> searcher.getIndexReader().getTermFreqVector(
> hits.id(i), "");
> StringBuilder str = new StringBuilder();
> for (String s : hits.doc(i).getValues("")) {
> str.append(s);
> str.append(" ");
> }
>
> System.out.println(str);
> TokenStream tokenStream = TokenSources.getTokenStream(v, false);
> String[] terms = v.getTerms();
> int[] freq = v.getTermFrequencies();
> for (int j = 0; j < terms.length; ++j) {
> System.out.print(terms[j] + ":" + freq[j] + ":");
>
> int[] pos = v.getTermPositions(j);
>
> System.out.print(Arrays.toString(pos));
>
> TermVectorOffsetInfo[] offset = v.getOffsets(j);
> for (int k = 0; k < offset.length; ++k) {
>
> System.out.print(":");
>
> System.out.print(str.substring(offset[k].getStartOffset(),
> offset[k].getEndOffset()));
> }
>
> System.out.println();
> }
> }
> searcher.close();
> If I run the above I get:
> one:1:[0]:one
> two:1:[1]: tw
> Note that the offsets for the second term are off by 1.
> It seems to be that the length of the value that is stored is not taken into
> account when calculating the offset for the fields of the next value.
> I noticed ths problem when using the highlight contrib package which can make
> use of term vectors for highlighting. I also noticed that the offset for the
> second string is +1 the end of the previous value, so when concatenating the
> fields values to pass to the hgighlighter I add to append a ' ' character
> after each string...which is quite useful, but not documented anywhere.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL
Should'nt searchables field in MultiSearcher be protected?
Hello All. In both MultiSearcher and ParallelMultiSearcher classes we have a searchables field : private Searchable[] searchables; Why this field is not "protected" in MultiSearcher? In this manner, we do not need this field in ParallelMultiSearcher anymore. Best Regards. -- View this message in context: http://www.nabble.com/Should%27nt-searchables-field-in-MultiSearcher-be-protected--tf4079312.html#a11594356 Sent from the Lucene - Java Developer mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-958) MultiSearcher Filtering with more than one index is broken
[
https://issues.apache.org/jira/browse/LUCENE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512714
]
Yonik Seeley commented on LUCENE-958:
-
Think of a Filter as symbolic rather than concrete (e.g. the set of documents
matching the query "inStock:true")
Filter.getBits is passed an IndexReader as an argument, and returns the actual
ids (via a BitSet) for that reader only.
Thus, an implementation that returns the same BitSet regardless of what
IndexReader it is passed is not going to work correctly.
> MultiSearcher Filtering with more than one index is broken
> --
>
> Key: LUCENE-958
> URL: https://issues.apache.org/jira/browse/LUCENE-958
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
>Affects Versions: 2.2
>Reporter: Ion Badita
>
> Using filtering on MultiSarcher with more than one index is not working right.
> Probable the best way to describe the problem is to give a small example:
> Suppose we have 2 Indexes with two documents each:
> Index1 {Doc(id:"A", content:".."), Doc(id:"B", content:"..")}
> Index2 {Doc(id:"C", content:".."), Doc(id:"D", content:"..")}
> When executing a query that returns all the documents and applying a
> QueryFilter that generated the following BitSet (1, 0, 0, 0), it should
> filter all the documents but first; the real results are: Doc(id:"A") and
> Doc(id:"B"), this because the MultiSearcher applies the BitSet filter from
> the bitset's position 0 for each Index.
> The right way is to split the bitset in peaces: Index1 to get the bites form
> 0-1 and Index2 bites from 2-3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-958) MultiSearcher Filtering with more than one index is broken
[
https://issues.apache.org/jira/browse/LUCENE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512706
]
Nicolas Lalevée commented on LUCENE-958:
I don't understand the invalid status of this issue. If the filter provided to
the multisearcher have to implement itself the document offset handling, then
there an API issue : MultiSearcher implements Searchable.
> MultiSearcher Filtering with more than one index is broken
> --
>
> Key: LUCENE-958
> URL: https://issues.apache.org/jira/browse/LUCENE-958
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
>Affects Versions: 2.2
>Reporter: Ion Badita
>
> Using filtering on MultiSarcher with more than one index is not working right.
> Probable the best way to describe the problem is to give a small example:
> Suppose we have 2 Indexes with two documents each:
> Index1 {Doc(id:"A", content:".."), Doc(id:"B", content:"..")}
> Index2 {Doc(id:"C", content:".."), Doc(id:"D", content:"..")}
> When executing a query that returns all the documents and applying a
> QueryFilter that generated the following BitSet (1, 0, 0, 0), it should
> filter all the documents but first; the real results are: Doc(id:"A") and
> Doc(id:"B"), this because the MultiSearcher applies the BitSet filter from
> the bitset's position 0 for each Index.
> The right way is to split the bitset in peaces: Index1 to get the bites form
> 0-1 and Index2 bites from 2-3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project lucene-java (in module lucene-java) 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 lucene-java has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. 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://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-14072007.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 -INFO- Failed to extract 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: 25 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=14072007 -Djavacc.home=/srv/gump/packages/javacc-3.1 package [Working Directory: /srv/gump/public/workspace/lucene-java] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/lucene-java/build/classes/java:/srv/gump/public/workspace/lucene-java/build/classes/demo:/srv/gump/public/workspace/lucene-java/build/classes/test:/srv/gump/public/workspace/lucene-java/contrib/db/bdb/lib/db-4.3.29.jar:/srv/gump/public/workspace/lucene-java/contrib/gdata-server/lib/gdata-client-1.0.jar:/srv/gump/public/workspace/lucene-java/build/contrib/analyzers/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/ant/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/benchmark/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/db/bdb/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/db/bdb-je/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/gdata-server/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/highlighter/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/javascript/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/lucli/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/memory/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/queries/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/regex/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/similarity/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/snowball/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/spellchecker/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/surround/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/swing/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/wordnet/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/xml-query-parser/classes/java:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/je-1.7.1/lib/je.jar:/srv/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-14072007.jar:/srv/gump/packages/javacc-3.1/bin/lib/javacc.jar:/srv/gump/public/workspace/jline/target/jline-0.9.92-SNAPSHOT.jar:/srv/gump/packages/jtidy-04aug2000r7-dev/build/Tidy.jar:/srv/gump/public/workspace/junit/dist/junit-14072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-14072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-14072007.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/srv/gump/packages/nek
[EMAIL PROTECTED]: Project lucene-java (in module lucene-java) 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 lucene-java has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. 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://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-14072007.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 -INFO- Failed to extract 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: 25 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=14072007 -Djavacc.home=/srv/gump/packages/javacc-3.1 package [Working Directory: /srv/gump/public/workspace/lucene-java] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/lucene-java/build/classes/java:/srv/gump/public/workspace/lucene-java/build/classes/demo:/srv/gump/public/workspace/lucene-java/build/classes/test:/srv/gump/public/workspace/lucene-java/contrib/db/bdb/lib/db-4.3.29.jar:/srv/gump/public/workspace/lucene-java/contrib/gdata-server/lib/gdata-client-1.0.jar:/srv/gump/public/workspace/lucene-java/build/contrib/analyzers/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/ant/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/benchmark/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/db/bdb/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/db/bdb-je/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/gdata-server/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/highlighter/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/javascript/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/lucli/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/memory/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/queries/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/regex/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/similarity/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/snowball/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/spellchecker/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/surround/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/swing/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/wordnet/classes/java:/srv/gump/public/workspace/lucene-java/build/contrib/xml-query-parser/classes/java:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/je-1.7.1/lib/je.jar:/srv/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/srv/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-14072007.jar:/srv/gump/packages/javacc-3.1/bin/lib/javacc.jar:/srv/gump/public/workspace/jline/target/jline-0.9.92-SNAPSHOT.jar:/srv/gump/packages/jtidy-04aug2000r7-dev/build/Tidy.jar:/srv/gump/public/workspace/junit/dist/junit-14072007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-14072007.jar:/srv/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-14072007.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/srv/gump/packages/nek
