So I’m back supporting this project again, very part-time. I recently pushed a 1.2.0 version with the long-awaited upgrade to Hibernate 4 and JPA 2. This upgrade is basically the only change in this release besides some internal refactoring.
As of Dec 2011, I am not currently supporting this project. I have been the sole owner of this project from the beginning, but I will no longer be following up on issues or making releases. At this point there is no one else to take over this responsibility, so it will not be happening. There are still some users who respond on the Google group. I apologize for the inconvenience.
If anyone would like to become a contributor and take charge of patches and releases, contact me and I can work with you on it. My contact info can be found here.
It is possible that I will return to the project at some time, but at this point it’s just not a technology stack that I am working with.
Version 1.0.0 of Hibernate Generic DAO (http://code.google.com/p/hibernate-generic-dao/) was released today. It has a few small bug fixes, but the big changes are the new build and deployment strategy and the new package names.
New Package Name
The root package name has been changed from com.trg to com.googlecode.genericdao. There area couple of considerations in this. First, TRG was a shortcut for The Revere Group, but The Revere Group’s domain is reveregroup.com not trg.com. Secondly, since this is an open source project, it makes sense to decouple it from the company where it originated, especially since none of the active developers work for that firm anymore.
Deployment to Maven Central
With version 1.0.0, the framework is finally available for your projects via the Maven central repository. This means all you have to do is add the dependency tag to your pom.xml–no more need to specify our custom repository. (See http://code.google.com/p/hibernate-generic-dao/wiki/MavenRepo for instructions.) Perhaps more importantly, it means we will be able to easily release snapshot builds from time to time between major releases. This is important when you need the latest bug fixes without waiting for the next major release (which tend to be few and far between). As part of this the whole release process has also been greatly simplified which means those major builds might actually come more often as we can spend more time developing fixes and features and less time messing with building and copying files and documentation around.
New Build Structure
The project used to be composed of about seven different components, each needing to be built separately (unless and IDE was used to build them all at once). The new set-up includes a single parent maven project that builds all of the seven individual components. The components are still available for individual use in other projects that depend on them, but when it comes to building the actual framework itself, it’s now just one command. This, again, will simplify releases, making them more frequent and robust.