Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.1-beta3
-
Fix Version/s: 1.2-M2
-
Component/s: Persistence
-
Labels:None
Description
There are a couple of non-criteria issues:
in beta 3 and snapshot, the Hibernate plugin always get automatically downloaded from the Internet. it's quite annoying. afaik, there is another issue abt that. I suppose, in the final release it will support non-Hibernate, so there will be a way to make Grails not to do the download.
real issues:
1. The current Hibernate annotations is 3.3.0, the latest is 3.4.0. It's nice to keep it up to date. And for my JPA Plugin, probably the Hibernate Entity Manager 3.4 requires Annotation 3.4. So when the Hibernate plugin snapshot is automatically downloaded, it adds an incompatible hibernate annotation to the classpath and cause startup error.
2. should the hibernate plugin includes: hibernate-entitymanager-3.4.0.jar ? it doesn't affect me too much as i could put the jar in my plugin. Just wonder if the hibernate plugin should contains a full set of Hibernate library so whoever want to use it could just depend on a single plugin. (e.g. for those guys who don't use GORM and JPA Plugin but use Hibernate entity manager directly)
workaround - manually remove the hibernate plugin:
1. at $projectRoot/application.properties, remove the line of plugins.hibernate
2. under $user_home/.grails/$grailsVersion/projects/$projectName/plugins/