Skip to content

Remove native support for Hibernate 3.6 and 4.x [SPR-13827] #18400

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 Dec 29, 2015 · 2 comments
Closed
Assignees
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Dec 29, 2015

Juergen Hoeller opened SPR-13827 and commented

Along with #18060, let's remove our orm.hibernate3 and orm.hibernate4 packages and also upgrade our HibernateJpaVendorAdapter accordingly.

Even at this point (end of 2015), Hibernate 5.x is the only actively maintained branch. By early 2017, Hibernate 4.x will only be found in legacy JBoss EAP environments.


Issue Links:

1 votes, 2 watchers

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

It would be helpful to upgrade to Hibernate 5.2+ right away, due to several API breakages there... However, since WildFly 10 / JBoss EAP 7 includes Hibernate 5.0.9 only and is not likely to upgrade to 5.2, it seems worth supporting Hibernate 5.0+ even in Spring Framework 5.

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

While only orm.hibernate5 stays around as of Spring 5.0, our JPA support - including HibernateJpaVendorAdapter and HibernateJpaDialect - remains compatible with Hibernate 4.3 (the minimum Hibernate release for JPA 2.1) for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants