Skip to content

Upgrade to JPA 2.1+ and Bean Validation 1.1+ [SPR-13481] #18060

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Sep 22, 2015 · 3 comments
Closed
Assignees
Labels
type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Sep 22, 2015

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:

@spring-projects-issues
Copy link
Collaborator Author

Alex commented

I report here a comment I put an a closed ticket: the hibernate team has already deprecated hibernate 4.x: http://in.relation.to/2015/10/27/great-jira-cleanup-2015/

"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.

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Dec 18, 2015

Juergen Hoeller commented

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.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Jul 4, 2016

Juergen Hoeller commented

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants