Note this would affect only our upcoming Hibernate Search 5.0: it's a
major release which breaks some backwards compatibility anyway. I
guess that blasts any remaining concern?
For the purpose of WFK users in maintenance mode I'll expect them to
stay on previous Search version, on which we'll backport fixes as
usual.
But I also expect we'll eventually want to provide a "new" version to
deliver the goodies of EE7, JPA 2.1, etc.. which all require JDK7
anyway (in the scope of WFK or anything else coming our way).
Thanks all for the comments
Sanne
On 20 March 2014 16:04, Burr Sutter <bsutter(a)redhat.com> wrote:
Adding the WFK Mareks :-)
The only potential problem that I see is backward incompatibility with WFK 2.0.0 and its
supported frameworks through June 2015.
We do not require JVM upgrades, in production, for customers, within the "supported
time window" - in our WFK case June 2012 to June 2015.
On Mar 20, 2014, at 11:21 AM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
> The next minor release of Apache Lucene v. 4.8 will require Java7.
>
> The Lucene team has highlighted many good reasons for that, including
> some excellent improvements in sorting performance and reliability of
> IO operations: nice things we'd like to take advantage of.
>
> Objections against baseling Hibernate Search 5 to *require* Java7 too?
> We hardly have a choice, so objections better be good ;-)
>
> -- Sanne