disableLocks

2002-06-25 Thread Stefan Bergstrand
Definitely no big deal, but: I think that the system property disableLocks should be named "disableLuceneLocks", or something that mentions which locks we are talking about. There might be some other type of locks handled in the same JVM, and it would be nice to make clear which locks we are t

Re: COMMENT REQUESTED: Lucene 1.2 Final Release

2002-06-25 Thread Dmitry Serebrennikov
I remember seeing something like that when I used an older version of Ant to compile Lucene. What Ant version were you using, Lex? Dmitry. Lex Lawrence wrote: > Maybe I'm off my rocker, or maybe I've overlooked something. > Regardless, if nobody else noticed anything I'll just drop it gracefu

Re: COMMENT REQUESTED: Lucene 1.2 Final Release

2002-06-25 Thread Lex Lawrence
Maybe I'm off my rocker, or maybe I've overlooked something. Regardless, if nobody else noticed anything I'll just drop it gracefully. -Lex >From: Otis Gospodnetic <[EMAIL PROTECTED]> >Reply-To: "Lucene Developers List" <[EMAIL PROTECTED]> >To: Lucene Developers List <[EMAIL PROTECTED]> >Subjec

Re: Bug? QueryParser may not correctly interpret RangeQuery text

2002-06-25 Thread Brian Goetz
> > Also, we talked about adding numeric ranges too. First we'd need a > > NumberField class and "constructor", similar to DateField, and then > > we'd want to use NumberFormat to see if the elements in the range query > > are of the right format. The only part I'm not sure about here is what to

Re: COMMENT REQUESTED: Lucene 1.2 Final Release

2002-06-25 Thread Otis Gospodnetic
I can't replicate that. I moved my jakarta-site2 away, renamed it, while I left the property in default.properties as: jakarta.site2.home = ../jakarta-site2 I don't get an error when doing 'ant jar', for instance. Maybe you can post your error message. Otis --- Lex Lawrence <[EMAIL PROTECTED

Re: Bug? QueryParser may not correctly interpret RangeQuery text

2002-06-25 Thread Peter Carlson
Brian, This sounds great. I'll have a look at it and hopefully have some time to help finish it up. Although I am a bit behind on a few Lucene project myself. --Peter On 6/24/02 5:09 PM, "Brian Goetz" <[EMAIL PROTECTED]> wrote: >> Just curious what the status of this issue is, as the discuss

cvs commit: jakarta-lucene/src/java/org/apache/lucene/document Field.java

2002-06-25 Thread otis
otis2002/06/25 09:18:32 Modified:src/java/org/apache/lucene/document Field.java Log: - Made a small method javadoc change. Revision ChangesPath 1.4 +1 -2 jakarta-lucene/src/java/org/apache/lucene/document/Field.java Index: Field.java ===

cvs commit: jakarta-lucene/src/java/org/apache/lucene/store FSDirectory.java

2002-06-25 Thread otis
otis2002/06/25 09:09:15 Modified:src/java/org/apache/lucene/store FSDirectory.java Log: - Reduced the number of condition checks for disabling locks. - Documented the use of 'disableLocks' system property in class Javadoc. Revision ChangesPath 1.8 +20 -18

Re: COMMENT REQUESTED: Lucene 1.2 Final Release

2002-06-25 Thread Lex Lawrence
Actually, this is the case (tested) if you use ANY Ant target. The failure occurs when constructing the path "anakia.classpath", which is not part of any target. It happens before processing even the "init" target, which a regular user would probably need. -Lex >This is probably (not tested)