Replies: 4 comments 3 replies
-
@gsartori Do you know of a work around for the following? Spring Boot 3.x switched to the jakarta.persistence package namespace of JakartaEE 9+, which is supported in Hibernate 6. Spring Boot 2.x uses the javax.persistence package namespace of JakartaEE 8 and earlier (JPA 2.2 and earlier) used in Hibernate 5.X. |
Beta Was this translation helpful? Give feedback.
-
Is Hibernate 6 a blocker to work on the next release of Grails? |
Beta Was this translation helpful? Give feedback.
-
Does anybody know if updating GORM 8 to Groovy 4 and Java 17/21 would be possible staying with Hibernate 5 without adopting Hibernate 6? |
Beta Was this translation helpful? Give feedback.
-
Hibernate started to support JPA 3.0 in version 5.5. All Hibernate artifacts that support the new JPA 3.0 APIs have the suffix “-jakarta” in their name.
https://in.relation.to/2021/06/04/hibernate-is-jakarta-jpa-2/ https://in.relation.to/2021/06/02/hibernate-orm-550-final-release/ |
Beta Was this translation helpful? Give feedback.
-
Hibernate 6 improves performances so it’s worth to consider moving ahead and supporting it. At the moment though we should consider the priority on security issues.
Databases are consolidated technologies, having the latest ORM is something that could wait.
Having the latest web framework cannot.
Beta Was this translation helpful? Give feedback.
All reactions