Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.3
-
Fix Version/s: None
-
Labels:None
-
Environment:N/A
-
Number of attachments :
Description
In Hibernate 3.0, currently alpha, the class structure has changed from net.sf.hibernate to org.hibernate. This means that when using this plugin the user has to change the dialect class in hibernate.cfg.xml or hibernate.properties before & after a hibernate:schema-export.
To upgrade this plugin to support 3.0 is very straightforward - just change the dependency, reorganise the imports & fix line 178 of SchemaBeanBase to support the new API method Configuration.addJar(File). There's also the 3.0 DTD's to add support for, but nothing major to get things working.
Obviously these changes will break 2.1 users, so is it worth maintaining parallel releases for both 2.1 and 3.0 Hibernate users?
Mark,
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