Add an annotation that allows per-site control over `org.hibernate.envers.revision_on_collection_change` behavior

Description

Currently the Envers configuration option org.hibernate.envers.revision_on_collection_change is global and when setting it affects all audited entities. It might be useful for specific scenarios to be able to influence this behavior at a per-site location using an annotation like @RevisionOnCollectionChange(boolean)?

Given

See https://stackoverflow.com/questions/59633260/hibernate-envers-prevent-version-on-onpostdelete

This way when the user creates a Soup with Ingredients and later deletes the Soup entity, the SOUP_AUD table won't end up with REVTYPE's 0, 1, and 2 but instead just 0 and 2.

Environment

None

Assignee

Chris Cranford

Reporter

Chris Cranford

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Priority

Major
Configure