|
|
|
I've modified the source to support hibernate 3.
I had to remove the code generation part as there is no hibernate extensions jar available on ibiblio. It's hasn't really been tested (other have the hibernate:schema-export goal). The changes only took 30 minutes... Cheers, Dan,
Unfortunately, the fix is not that simple, as such change would cease the support to Hibernate 2.x. In other words, we need to decide how to support both versions (Hibernate 2 and 3). – Felipe Maybe a hibernate3 maven plugin? I wouldn't much more will be happening with hibernate2.x...
This patch provides full seamless compatibility between both 2.x and 3.x versions of Hibernate. After this patch the plugin no longer has a hibernate dependency. The user of the plugin chooses the version that will be supported by placing the hibernate dependency in their project.xml file. The plugin detects the hibernate version and acts accordingly. It also fails imediately if hibernate is not found as a dependency. The one extra class I created, HibernateVersions, is a reflective bridge to detect the correct classes and deal with the minor API changes between the versions. After adjusting the dependencies of the "simpleTest" it passed fine. I also added a new test "simplev3Test", just a copy with everything updated to use version 3.0.1. It passes just fine also.(JTA is needed locally) The codeGeneration test always failed for me, even before I began working. I excluded it from the reactor in the plugin-test directory. I believe the codeGeneration in 2.X will work just fine. I think the test is not set up correctly. -Anthony Vito
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yes, if it breaks compatibility, we better have 2 branches in parallell (probably 2.0/main for the hibernate 3.0 and 1.x for the old hibernate).
– Felipe