On Jul 22, 2010, at 17:52, Bill Janssen <jans...@parc.com> wrote:
Andi Vajda <va...@apache.org> wrote:
On Jul 22, 2010, at 2:09, Bill Janssen <jans...@parc.com> wrote:
Andi Vajda <va...@apache.org> wrote:
Porting your stuff to 3.0 is thus highly recommended instead
of complaining about broken (my bad) long- deprecated APIs.
Hey, take 2.9.3 down, and announce no further pylucene support for
2.x,
and I'll stop talking about it.
The value in 2.9.3 is really just in the Lucene fixes since 2.9.2. If
you want them without the new JCC which is tripping you up, take a
2.9.2 build tree and change the Lucene svn url near the top of the
Makefile to point at the 2.9.3 sources. This should "just work" (tm).
Another fix is to edit the common-build.xml file in the Lucene subtree
to remove the 1.4 restriction. That lets it build with Java 5 and
that
adds the Iterable interface, and things work as they did, even with
jcc 2.6.
Even better. Still, none of the Lucene 2.9 code uses any of the Java
1.5 features directly, hence why Lucene 3.0 is yet a better choice.
Andi..
Bill
