Tags
Authors
I have just finished releasing Hibernate O/RM 5.0.0.Beta2. Beyond Beta1, this release adds:
We just got done releasing Hibernate O/RM 5.0.0.Beta1. I will follow up later with a more in depth blog post for 5.0.0.Final, but this first Beta implements all new APIs and most new features. Specifically in this Beta include:
I have just released 4.3.1.Final, the first bugfix release for Hibernate ORM 4.3. In addition to bug fixes, a few improvements of note include:
The Hibernate team is proud to announce the Hibernate ORM 4.3.0.Final Release. With this release, Hibernate is now a certified implementation of the JPA 2.1 specification. Certified awesomeness!
The Hibernate team is proud to announce the 4.3.0.CR1 release of Hibernate ORM. This is the first release candidate for 4.3 and JPA 2.1 support. For those who maybe are not familiar with our release methodology, this means that in 2-3 weeks this release will essentially be re-tagged as Final unless some critical bugs are reported with it in the meantime.
Version 4.3.0.Beta5 release of the Hibernate ORM project has just been released. This is a step closer towards JPA 2.1 compliance, but also lots of other goodies. JPA 2.1 work of note includes:
Back to work after summer fun :)
The Hibernate team is pleased to announce today's release of Hibernate 4.3.0.Beta3. Support for entity graphs is still a work in progress, but all other JPA 2.1 features should be fully operational. Specific JPA 2.1 features fully functional as of this release include:
At flush-time, Hibernate needs to know what entity state has become dirty (changed) so that it knows what data needs to be written to the database and what data does not. Historically Hibernate only defined one means of such dirtiness checking, but has since added multiple additional schemes which seem to be not as well known. The intent for this blog is to start a base for improving the documentation around dirty checking and these various options.
