Maybe I'm way off-base in my understanding of this but here are my 2 cents to chew on. This seems to be more of an issue in how Hibernate constructs, configures, references, and implements the generators. The @GeneratedValue name is a reference to a global generator for a persistence unit so referring to it from multiple annotations shouldn't generate duplicate errors. The @SequenceGenerator defines the parameters that should be "passed" to the referenced identifier generator and so also shouldn't generate duplicate errors. The objects needed/created/referenced by the persistence provider to support this should be irrelevant to generating errors/warnings about the configuration. Not looking for response, more or less venting about the "duplicates" being logged as warnings.

Applied both pull requests (5.3 and 5.2)

To clarify... we all agree that the JPA requirement is goofy, hence the compliance setting.

The proposed solution, see PR is to add a new configuration setting hibernate.jpa.compliance.global_id_generators whose default value is false.

@Emmanuel Bernard Both JPA 2.1 and JPA 2.2 specification state for TableGenerator and SequenceGenerator annotations that "The scope of the generator name is global to the persistence unit (across all generator types)"