Build failed in Hudson: Lucene-trunk #528

See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/528/changes Changes: [gsingers] updated to run on hudson.zones -- [...truncated 6190 lines...] [junit] Testsuite: org.apache.lucene.queryParser.TestQueryParser [junit] Tests run: 25, Failur

[jira] Updated: (LUCENE-1282) Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene

[ https://issues.apache.org/jira/browse/LUCENE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated LUCENE-1282: - Comment: was deleted > Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene >

[jira] Issue Comment Edited: (LUCENE-1282) Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene

[ https://issues.apache.org/jira/browse/LUCENE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600165#action_12600165 ] mikemccand edited comment on LUCENE-1282 at 7/16/08 5:00 PM: ---

[jira] Commented: (LUCENE-1282) Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene

[ https://issues.apache.org/jira/browse/LUCENE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614161#action_12614161 ] Ismael Juma commented on LUCENE-1282: - As can be seen in the Sun database a fix for th

[jira] Commented: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput

[ https://issues.apache.org/jira/browse/LUCENE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614074#action_12614074 ] Brian Gardner commented on LUCENE-753: -- This probably doesn't help much, but I impleme

Re: CorruptIndexException docs out of order

Thanks. Yes what you said is correct. There were two bugs, one in the patch and a few in Ocean since fixed. On Fri, Jul 11, 2008 at 7:49 PM, Michael McCandless < [EMAIL PROTECTED]> wrote: > > I think if your SegmentReader is not returning the right result when > numDocs() is called it can lead

[jira] Commented: (LUCENE-1337) [PATCH] improve searching under high concurrancy

[ https://issues.apache.org/jira/browse/LUCENE-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614031#action_12614031 ] Yonik Seeley commented on LUCENE-1337: -- Thanks Brian, also see LUCENE-753 for more hi

[jira] Updated: (LUCENE-1337) [PATCH] improve searching under high concurrancy

[ https://issues.apache.org/jira/browse/LUCENE-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Gardner updated LUCENE-1337: -- Attachment: lucene.patch This patch applies to version 2.3.1 > [PATCH] improve searching unde

[jira] Created: (LUCENE-1337) [PATCH] improve searching under high concurrancy

[PATCH] improve searching under high concurrancy Key: LUCENE-1337 URL: https://issues.apache.org/jira/browse/LUCENE-1337 Project: Lucene - Java Issue Type: Improvement Components: Se

RE: maven snapshot repository

Hi Grant, On 07/16/2008 at 12:39 PM, Grant Ingersoll wrote: > I did run publish-maven.sh by hand and I see the items in the snapshot > repo. When I look at the lucene-core directory in the snapshot repo via the web interface, I don't see any 2.4-SNAPSHOT stuff - just the 2.3-SNAPSHOT dir that w

Re: maven snapshot repository

OK, I think it should work now. Let's keep an eye out to make sure the cron job runs tomorrow morning (~5am PST, I think) I did run publish-maven.sh by hand and I see the items in the snapshot repo. On Jul 16, 2008, at 12:08 PM, Grant Ingersoll wrote: I take that back, I was looking on th

Re: maven snapshot repository

I take that back, I was looking on the wrong account. It is running. I'll fix it. On Jul 16, 2008, at 12:05 PM, Grant Ingersoll wrote: On Jul 14, 2008, at 1:22 PM, Steven A Rowe wrote: Looking into this further, I can see that the nightly jars are being produced properly - for example, l

Re: maven snapshot repository

On Jul 14, 2008, at 1:22 PM, Steven A Rowe wrote: Looking into this further, I can see that the nightly jars are being produced properly - for example, lucene-core is labeled 2.4- SNAPSHOT, and the files are dated today:

[jira] Updated: (LUCENE-1314) IndexReader.reopen(boolean force)

[ https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1314: - Attachment: lucene-1314.patch lucene-1314.patch Fixed bug in SegmentReader.reopenSegmen

TokenStream problem?

According to the documentation for TokenStream, derived classes are to override either next() or next(Token). Currently, if next(Token) is overridden, but next() is called, payload is cloned if it exists in the new token. However, if next(Token) is called, it is up to the implementation to p