Release Announcement — Coherence Hibernate 3.0.0 and 2.3.3
Adding support for Hibernate 6.2, Java 17+ and Jakarta EE
We are stoked to announce the simultaneous release of Coherence Hibernate 3.0.0 and 2.3.3!
What’s new in Coherence Hibernate 3.0.0
This release of Coherence Hibernate adds support for Hibernate 6.x including the latest release 6.2.6.Final by adding the new coherence-hibernate-cache-6 Maven module. This release is also the first release targeting Jakarta EE Apis. All Cache SPI modules that do not support Jakarta EE have been removed and as a result only the following two modules remain:
- coherence-hibernate-cache-53 (Hibernate 5.6.x)
- coherence-hibernate-cache-6 (Hibernate 6.1.x & Hibernate 6.2.x)
In this release, all library dependencies have been updated to Jakarta EE supporting versions. This includes updating the Coherence dependency to 23.03. This means that Java 17 is now the baseline version for Coherence Hibernate.
Recognizing that applications that use Java EE Apis are still widely used, we will continue to provide Java EE support via the Coherence Hibernate 2.3.x branch on GitHub and its respective releases. Nonetheless, we encourage everyone to migrate to Jakarta EE as soon as possible.
For a detailed list of changes, please refer to the release notes on GitHub. The documentation for Coherence Spring 4.0.0 is available here.
What’s new in Coherence Hibernate 2.3.3
Coherence Hibernate 2.3.3 contains mostly minor version updates, e.g. we upgraded the Coherence version to 22.06.4 and also upgraded the Hibernate dependency for the 5.3 module to 5.6.15.Final. Keep in mind that Coherence Hibernate 2.3.x will continue to support the Java EE Apis.
For a detailed list of changes, please refer to the release notes on GitHub.
Contribute to Coherence Hibernate!
We would love to hear from you! Please take Coherence Hibernate and Coherence CE for a spin! If you have questions, please join our Slack channel or ask questions on Stack Overflow. If you see missing features or if you have any other suggestions for improvement please contact us, e.g. via Twitter @OracleCoherence or feel free to file a GitHub issue. Contributions are always welcome!
