I wouldn't disagree on requiring Java 7.
I probably wouldn't disagree with Java 8 either, after all we're not
removing older versions of Hibernate from any download location and
we'll still support and maintain some older versions. It would
actually be nice to have the latest ORM version to be able to
experiment with significant API improvements.
FYI Hibernate Search is requiring Java 7 already, and our CI servers
are already testing our projects with JDK9 as well.
That said, Java 6 is still being supported by some vendors. Not by
Oracle, but Red Hat and SAP will support it for much longer.
-- Sanne
On 1 April 2015 at 01:04, Steve Ebersole <steve(a)hibernate.org> wrote:
So we now have to deal with a multi-jdk build in Hibernate ORM. We
need
Java 8 in order to compile the new hibernate-java8 module.
I wanted to remain compatible with Java 6 for the rest. However, I ran
into a snag there because of JAXB which we now use (in conjunction with
StAX) to process XML in ORM. ANyway, the JAX generation creates a model
that is only compatible with Java 7. I have not yet had time to
investigate this deeply. But it has to do with a change in the definition
of javax.xml.bind.annotation.XmlElement and a change in its definition
between 1.6 and 1.7 to add a new
attribute javax.xml.bind.annotation.XmlElement#required.
If anyone is familiar with this situation, I'd love to hear some options
before I spend a lot of time investigating it.
The other option is that we say we are going to drop Java 6 support since
it has been unsupported now for, what, 3 years?
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev