You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By the time of Spring Framework 5.0 GA, JPA 2.1 and Bean Validation 1.1 will be almost four years old already. Since we tend to avoid compatibility compromises for Spring 5 now, let's enforce JPA 2.1 and Bean Validation 1.1 as a baseline. This includes upgrading the system requirements to Hibernate ORM 5.0+, Hibernate Validator 5.0+, EclipseLink 2.5+, and hopefully also to a yet-to-appear OpenJPA revision (otherwise we'd have to drop OpenJPA support if it remains stuck with JPA 2.0).
"Now that ORM 5.0 has gone final, we need to focus our development efforts on 5.0 and beyond.
http://github.com/hibernate/hibernate-orm/wiki/Huge-Project,-Small-Team discusses why we do this.
Put simply, versions prior to 5.x are no longer maintained and bug reports which do not affect 5.0 are outside that focus."
So with Spring 5 I suppose you should use Hibernate 5.x as a baseline.
Point taken, we should take that as a hard reason for going Hibernate 5.0+ in Spring 5.0. The JPA 2.1+ baseline implies Hibernate 4.3+ anyway, so this is an easy jump to make in early 2017... when the Hibernate team will have left 4.x in "unmaintained" state for 1.5 years already.
See #18400 for the dedicated Hibernate step to take there.
Addressed along with #18400, with Hibernate ORM 5.2 and Hibernate Validator 5.2 being used by default in spring-orm and spring-context now, respectively.
Juergen Hoeller opened SPR-13481 and commented
By the time of Spring Framework 5.0 GA, JPA 2.1 and Bean Validation 1.1 will be almost four years old already. Since we tend to avoid compatibility compromises for Spring 5 now, let's enforce JPA 2.1 and Bean Validation 1.1 as a baseline. This includes upgrading the system requirements to Hibernate ORM 5.0+, Hibernate Validator 5.0+, EclipseLink 2.5+, and hopefully also to a yet-to-appear OpenJPA revision (otherwise we'd have to drop OpenJPA support if it remains stuck with JPA 2.0).
Issue Links:
The text was updated successfully, but these errors were encountered: