Sure, we can wait to drop Java 8 if you all feel strongly about it,
but give my proposal a chance :)
Let me address a couple random points:
Java version 9 and 10 are not useful versions to support: only 8 and
11 have long term support, so 9 and 10 are already out of support. All
surveys I've seen
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
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
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 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