In Relation To

We are pleased to announce completion of the first phase of migrating Hibernate.org to what we feel will be a more stable, more collaborative and more friendly experience.

We have just released 3.5.0-CR-2. The main focus for this release was bugfixes and documentation.

I am pleased to announce that we have just released Hibernate version 3.5.0-CR-1. As a refresher, Hibernate follows the JBoss versioing scheme where CR is a Candidate for Release (what many of you might call RC). The main stated goal of 3.5 is JPA 2 compliance. This is the first release we believe achieves that goal entirely. In fact we are in the process of certifying for standalone JPA 2 compliance and have integrated this CR into the imminent JBoss AS M2 release as part of their effort towards full Java EE 6 compliance.

There have been numerous questions in regards to the following statement made in a few places on the Hibernate website:

In terms of JPA 2, its really easier to start talking about things not yet implemented :) The set of missing features are defined by the unresolved subtasks of the following 2 Jira issues:

Specific JPA 2 related enhancements from Beta-2 include:

The second release towards JPA 2 support. Specific JPA 2 related enhancements from Beta-1 include:

As a follow up to http://in.relation.to/Bloggers/SimultaneouslySupportingJDBC3AndJDBC4WithMaven, I wanted to point out that I uploaded some example projects to the design discussion. There are 2 different approaches as Maven projects and one Gradle project.

At some point between August and September there appears to have been a number of incorrect auto-unsubscriptions against some of the Hibernate mailing lists (hibernate-dev for sure). I am not going to point fingers as to who is to blame in this. I do however apologize for any inconvenience this might have caused. If you find yourself part of this group, the current direction I am receiving is that you will just have to re-subscribe :( if you happen to still have the unsubscribe notification email I would be very interested in getting it to pass along to our mailman admins; you can forward them to me directly.

Per HHH-2412 and its design discussion I have been working on supporting JDBC4 in Hibernate. Initially I had planned on adding this in 3.6, but now leaning toward 3.5 Anyway, as outlined on the design wiki, I initially thought to add this support as separate modules. However, I quickly came to the realization that using separate modules would actually require users make an explicit choice wrt an extra jar. Especially considering that I could make Hibernate code make this determination programatically, I really did not like that aspect to using modules here. So I started looking for alternatives.