|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Envers modifications depend strongly on Hibernate Tools. I don't mind moving org.hibernate.tool.ant.EnversHibernateToolTask class to org.hibernate.envers.ant package. We could a) introduce public getter/setter for configurationTask property, or b) change its access modifier to protected. IMO Max would be the best person to decide on one of the options. EnversSchemaGenerator shall be moved as well. This would allow to delete org.hibernate.tool package from Envers module.
While moving Envers classes, remember to update documentation in documentation/src/main/docbook/devguide/en-US/Envers.xml.