[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5551?page=c... ] Erik-Berndt Scheper commented on HHH-5551: ------------------------------------------ In terms of usability, this would be a great idea. However, I assume backwards compatibility needs to be preserved, without the listeners being applied twice. But I am wondering if a new setting is required at all. I imagine this 'automatic enabling of Envers' requires some sort of classpath scanning (to check if the listeners are available). Doesn't it seem logical to assume that if a developer explicitly adds hibernate-envers.jar to the classpath, that he probably wants to use this jar as well? I.e. if hibernate-envers.jar is available on the classpath, then the listeners could be enabled by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5551?page=c... ] Steve Ebersole updated HHH-5551: -------------------------------- Assignee: Steve Ebersole -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5551?page=c... ] Steve Ebersole updated HHH-5551: -------------------------------- Fix Version/s: (was: 3.6.0.CR1) 4.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira