Upgrade to Grails 2.4, using the Hibernate 4 plugin. #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a comprehensive upgrade to Grails 2.4 and Hibernate 4. I used Grails 2.4.4, and hopefully made the plugin compatible with all Grails 2.4 releases.
Updated the configuration so that run-app works correctly.
Updated all tests to use current annotation-based conventions, and all tests pass.
Use aether, and the new release plugin so that packaging the plugin and releasing it to a repository works correctly.
Added an example test that shows a workaround for Enums, because I think there is an underlying envers bug with the current version that stores the Enum as an ordinal inside of the envers table, while storing the original value as a string.
Suggest converting the plugin version to match the current Envers version, so that it is easier to determine which versions of the Hibernate plugin it is associated with.
This checkin is designated a SNAPSHOT so would need an additional change to the EnversGrailsPlugin version to make it a released version.
We are using this snapshot version internally successfully.
Thank you!