In Relation To

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.

This is the first release towards supporting JPA 2. Most of the APIs are implemented. Some know limitations for this beta include:

Let me preface this by saying up front that, yes, I am fed up with Maven. In the 2 years since I decided to switch Hibernate over to use Maven for its build tool I don't think that Maven has lived up to making builds any easier. Quite the contrary, in fact. Previously though there was not really been any other option. At that time ant/ivy combo was just starting to gain traction. Not to mention that I do like the notion of build-by-convention which Ant just does not provide.

Just got done releasing 3.3.2 with tons of fixes/enhancements/improvements including some much needed documentation updates and again building translated docs.

I just pushed a new Hibernate Core maintenance release 3.2.7 for download. It is mostly minor fixes and improvements; check out the specifics in the change log either in Jira or SourceForge.

<queue-voice-of-god>In the beginning there was jdocbook-styles...</queue-voice-of-god>

Quite a few folks have asked about the new Hibernate Core modules introduced with the 3.3 release: what each is for, when to use which, etc. I wanted to take a bit to describe what each of the main modules is for and when/how you would use certain combinations. (These modules also define maven artifacts; all Hibernate Core artifacts use org.hibernate groupId).