An ANT user on the forums got in trouble several times, first with
Lucene versions vs Hibernate Search, then fixed that he upgraded ORM
to 5 as well to align with Search 5 only to see Validator blow up at
I'm thinking if we should invest a little time in developing a way to
detect a non-compatible version on classpath. We obviously can't make
that perfect as projects can't know the future, but we could get a
decent error message for the most common mistakes, for example major
What about the Hibernate ORM 'Integrator' mechanism to have a way to
define for example:
- expected ranges of ORM which *should* work (based on our
- expected versions which definitely work (being tested and released with)
- some kind of blacklist capability to list specific versions (or
ranges) which are known to definitely not work
This could be for example an annotation we use on our Integrator
Not aiming at a perfect solution of course - but it's better than
nothing. The open question is if this is worth our time, but maybe
it's an easy improvement?
On 29 April 2015 at 13:00, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
Yes I think a 5.x supporting ORM 5 would be my preference. I sort of
remember us discussing that option in AMS.
> On 29 Apr 2015, at 12:42, Sanne Grinovero <sanne(a)hibernate.org> wrote:
> Ok so we have all been wrong, but also we couldn't wait.
> Looking forward, does this mean you'd prefer to upgrade to ORM 5 in a
> minor version of Hibernate Search?
> On 29 April 2015 at 10:07, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
>> I liked and still do like the planet alignment to make the major a platform
signal. But when we discussed it, you all were against me.
>>> On 22 Apr 2015, at 10:41, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>>> Just a heads up: I'm not seeing the question from the subject often
>>> In fact, I only see it when I suggest to upgrade when helping some
>>> user. It's like they are very surprised "no way, I didn't think
>>> was possible?!"
>>> I think I've been hammering this information in each and every release
>>> blog, but apparently an assumption on major versions needing to be
>>> aligned is stronger.
>>> I guess we should embrace that? We can upgrade a minor of Hibernate
>>> Search to use Hibernate ORM 5 when it comes, that will fix the
>>> alignment of planets.
>>> Still, we also had hopes for a quick version 6 ..
>>> Just some thoughts.
>>> hibernate-dev mailing list