Hello!
I think it is a very good idéa to go for Lucene 2.3.1 as soon as possible,
since this version fixed a corruption issue introduced in 2.3.
Se snipped text below:
---
Release 2.3.1 of Lucene Java is now available!
This r
Just to let you know. Hibernate Search does not use the Lucene
features fixed by 2.3.1. So no corruption will happen if you stay in
a pure Hibernate Search environment. But year, moving to Lucene 2.3.1
is probably something that should be done :)
On Feb 25, 2008, at 07:51, Aleksander M. St
I think people mainly just "hacked it" from the previous pom. You
could do that approach, or start with the stuff currently in core/
trunk although many of the dependencies have changed there.
On Feb 20, 2008, at 5:41 PM, Max Bowsher wrote:
Looking at MAVENUPLOAD JIRA, it looks like for Hibe
On Sun, 24 Feb 2008 22:10:34 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
I think Hibernate Search should go for 3.1 from now one in trunk:
Cool.
- Hardy started working on the Null marker value and this requires
some compatibility changes
Well, I started on it and think it is not
- Hardy started working on the Null marker value and this
requires some compatibility changes
Well, I started on it and think it is not too hard, but Emmanuel
recommended to wait until 3.1. I will look into it again, but will
be very busy until mit March.
Another issue which I wold li
