To clarify some more... the regression here would be in the non-compliant naming strategy (now org.hibernate.boot.model.naming.ImplicitNamingStrategyLegacyJpaImpl). My guess is that even with 4.3, if you enable the JPA-compliant naming strategy you'd get the same error.