Tags
Authors
Back to work after summer fun :)
Hibernate ORM 4.2.5.Final was just released, containing about a dozen bug fixes. The vast majority of them were community contributions through pull requests -- thank you! Please see the full changelog for more information: https://hibernate.atlassian.net/issues/?jql=project=10031+AND+fixVersion=13953
Hibernate ORM 4.2.4.Final was just released, containing multiple bug fixes. Please see the full changelog for more information: https://hibernate.atlassian.net/issues/?jql=project=10031+AND+fixVersion=13750
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:
Hibernate ORM 4.2.1.Final and 4.1.12.Final were just released. The full changelogs can be viewed here: 4.2.1.Final and 4.1.12.Final
Previously, setting up a Hibernate ORM development environment in Eclipse was a pain. Many of you have complained about circular dependencies, generated sources not added to the classpath, etc. We recently cleaned up the 'gradle eclipse' task in HHH-7617 (1). If you're interested in getting started with Hibernate contributions, here's the easiest way to do it. Note that this requires 4.2.1-SNAPSHOT, 4.3.0-SNAPSHOT, or later:
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.
