lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <ysee...@gmail.com>
Subject Re: Lucene 1.9 and Java 1.4
Date Wed, 28 Sep 2005 13:46:33 GMT
I think your best bet for supporting Java 1.3 would be sticking with Lucene
1.4.

> One of the new classes that I am using is the ConstantScoreQuery. I am not
> sure if this is going to be included in Lucene 1.9 or not but this does
> make use of Java 1.4.

w.r.t. java.util.BitSet, it's a pain, and I plan a faster/better
replacement.

-Yonik
Now hiring -- http://tinyurl.com/7m67g

On 9/28/05, Paul.Illingworth@saaconsultants.com <
Paul.Illingworth@saaconsultants.com> wrote:
>
>
>
>
>
> Dear all,
>
> I have been trying to follow some of the developments for the new version
> of Lucene (1.9?). My understanding is that this will require Java 1.4. Is
> this correct? Is this because of changes to "core" functionality within
> Lucene or is it because some new additional classes require Java 1.4? If
> it's the latter then would it be possible to produce a custom build of
> Lucene that omits the classes that require Java 1.4?
>
> As you can probably guess from this that I have to support an older
> version
> of Java for certain platforms (Java 1.3.6). I don't know if I am unusual
> in
> this respect or if it is a common requirement.
>
> One of the new classes that I am using is the ConstantScoreQuery. I am not
> sure if this is going to be included in Lucene 1.9 or not but this does
> make use of Java 1.4. I have modified this to produce a version that works
> with pre 1.4 Java but probably at the expense of performance. I could
> submit this but if Lucene is going (has gone?) the 1.4 route there would
> be
> little point.
>
> Regards
>
> Paul I.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message