1 of 1 people found this helpful
I'm afraid not, other than modifying the source.
What would be your suggestion? move to Hibernate 3.3 and Envers 2.2.0, or better to move to higher version of Hibernate it-self (Envers included in the Hibernate 3.5 release onwards)
I do see potential backward refactoring issues if we move to Envers 2.2.0, because of repackaging and change in name for annotations like versioned -> audited. My question, is there any potential refactoring required for Hibernate also if we move?
Awaiting for your reply.
I would definitely move to a newer Hibernate version, preferrably 4.x. The 3.3, 3.5 branches are no longer maintained. I don't think there would be a lot of work regarding changing the Hibernate version itself.