Build failed in Hudson: Lucene-trunk #995

2009-10-31 Thread Apache Hudson Server
See -- [...truncated 3260 lines...] javacc-notice: jflex-uptodate-check: jflex-notice: common.init: build-lucene: build-lucene-tests: init: clover.setup: clover.info: clover: common.comp

Re: [VOTE] Release Apache Lucene Java 2.9.1, take 3

2009-10-31 Thread Yonik Seeley
On Thu, Oct 29, 2009 at 7:27 PM, Michael McCandless wrote: > OK, let's try this again! > > I've built new release artifacts from svn rev 831145 (on the 2.9 > branch), here: > >  http://people.apache.org/~mikemccand/staging-area/rc3_lucene2.9.1/ > > Changes are here: > >  http://people.apache.org/~

Lock API, throwing IOException

2009-10-31 Thread Sanne Grinovero
Hello, I'm implementing a distributed directory based on Infinispan (www.jboss.org/infinispan) currently implementing the org.apache.lucene.store.Lock, I was wondering why is /** Returns true if the resource is currently locked. Note that one must * still call {...@link #obtain()} before usin

[jira] Commented: (LUCENE-2019) map unicode process-internal codepoints to replacement character

2009-10-31 Thread Robert Muir (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772247#action_12772247 ] Robert Muir commented on LUCENE-2019: - Earwin, it won't mess with anyones attempt if t

[jira] Commented: (LUCENE-2019) map unicode process-internal codepoints to replacement character

2009-10-31 Thread Earwin Burrfoot (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772246#action_12772246 ] Earwin Burrfoot commented on LUCENE-2019: - bq. if you disagree with this patch, th

Re: contrib and lucene 3.0

2009-10-31 Thread Grant Ingersoll
On Oct 30, 2009, at 4:49 PM, Robert Muir wrote: I don't want to come across as negative here... i'm not trying to single anyone out, just a bit confused as to why my issue was singled out when theres already been both new features and new deprecations added to 3.0, and the issue in quest