javadoc output

2006-09-18 Thread Paul Elschot
Dear readers, In my working copy there are currently 794 lines of output from ant javadocs, mostly warnings/errors. Would it be possible to cut that down? Regards, Paul Elschot - To unsubscribe, e-mail: [EMAIL PROTECTED] For

[jira] Commented: (LUCENE-672) new merge policy

2006-09-18 Thread Yonik Seeley (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-672?page=comments#action_12435556 ] Yonik Seeley commented on LUCENE-672: - Should lowerBound start off as -1 in maybeMergeSegments if we keep 0 sized segments? new merge policy

[jira] Commented: (LUCENE-672) new merge policy

2006-09-18 Thread Ning Li (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-672?page=comments#action_12435571 ] Ning Li commented on LUCENE-672: Should lowerBound start off as -1 in maybeMergeSegments if we keep 0 sized segments? Good catch! Although the rightmost disk

[jira] Commented: (LUCENE-672) new merge policy

2006-09-18 Thread Yonik Seeley (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-672?page=comments#action_12435579 ] Yonik Seeley commented on LUCENE-672: - No need to submit a new patch... I made the change and committed it. new merge policy

[jira] Commented: (LUCENE-532) [PATCH] Indexing on Hadoop distributed file system

2006-09-18 Thread Otis Gospodnetic (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-532?page=comments#action_12435583 ] Otis Gospodnetic commented on LUCENE-532: - I'm hesitant to commit without the CFS support. It looks like more and more people are using CFS indexes.

[jira] Resolved: (LUCENE-632) The creation of a spell index from a LuceneDictionary via SpellChecker.indexDictionary (Dictionary dict) fails starting with 1.9.1 (up to current svn version)

2006-09-18 Thread Otis Gospodnetic (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-632?page=all ] Otis Gospodnetic resolved LUCENE-632. - Fix Version/s: 2.0.0 Resolution: Fixed If I understood all the comments correctly, there is no bug in HEAD. If I misunderstood, feel free to

Re: javadoc output

2006-09-18 Thread Simon Willnauer
I guess you build the java docs using a java 1.5 jvm and the gdata docs are build as well. The gdata code uses lots of java-doc links ([EMAIL PROTECTED] and @see) to third-party libs which is not nice. The ant task can not resolve this dep. and creates a lot of warnings. It is on top of the list

Re: javadoc output

2006-09-18 Thread Paul Elschot
On Tuesday 19 September 2006 00:01, Simon Willnauer wrote: I guess you build the java docs using a java 1.5 jvm and the gdata docs are build as well. Indeed. The gdata code uses lots of java-doc links ([EMAIL PROTECTED] and @see) to third-party libs which is not nice. The ant task can