Hi all,
[meta: I had this email as a draft on hold since a year; very glad to
finally be able to send it.]
We're usually quite conservative in dropping support for older JDKs
within the Hibernate team, but there's an increasing maintenance (and
development) cost when keeping older JDK compatibili
Hey,
I'm not sure it is a good idea to do this for Hibernate ORM 6 already as
that would probably hinder adoption. Some projects just didn't update to
Java 9+ yet because using the newer versions would have no real benefit.
We can use the Multi-Release JAR feature to make use of JDK features
i
Hi,
I share Christian's concerns; Hibernate Search 6 is already a huge change
for users, so I'm not sure reducing our potential user base even further by
requiring JDK11 is a good idea.
I don't have numbers, but from my understanding a lot of people are still
on JDK8, be it only because of the wh
I also think ORM 6 is not the time to do this. Especially moving to Java
11.
I think it is worthwhile though to discuss possibly moving to Java 9 to
take advantage of multi-release jars as Christian mentioned. But Java 9
has its own set of difficulties for adoption with modules. It is a
tough c
