We are using Hibernate with JPA.
We annotate attributes, not methods.

After upgrading from 5.0.3 to 5.0.4 Hibernate crashes with

javax.persistence.PersistenceException: Unable to build entity manager factory
at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:66)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)
at XYZTest.setup(XYZTest.java:35)
Caused by: org.hibernate.boot.MappingException: HHH000474: Ambiguous persistent property methods detected on XYZ; mark one as @Transient : [public java.lang.Boolean XYZ.getUngueltig()] and [public java.lang.Boolean XYZ.isUngueltig()] : origin(XYZ)
at org.hibernate.cfg.PropertyContainer.initProperties(PropertyContainer.java:201)
at org.hibernate.cfg.PropertyContainer.<init>(PropertyContainer.java:83)
at org.hibernate.cfg.InheritanceState.getElementsToProcess(InheritanceState.java:217)
at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:710)
at org.hibernate.boot.model.source.internal.annotations.AnnotationMetadataSourceProcessorImpl.processEntityHierarchies(AnnotationMetadataSourceProcessorImpl.java:245)
at org.hibernate.boot.model.process.spi.MetadataBuildingProcess$1.processEntityHierarchies(MetadataBuildingProcess.java:222)

Application code has not changed for years. Do we now have to annotate methods with @Transient? Up to now we only annotate attributes. Bug or feature?
Thanks a lot!

Can you please open a thicket on https://hibernate.atlassian.net providing a test case reproducing the issue?

Thanks a lot

I also experienced this with 5.0.4 but it was more of a problem with our code: We had an entity with a Boolean object field ("active") and there were both an isActive() method and a getActive() method. Since the column was declared not null anyway, I just used a boolean primitive and removed the getActive() method. All works fine now.

Yes, same for us, it was the opposite of "clean code", and I "solved" the problem by removing the second method "getUngueltig"...

But I think the problem has been fixed with Hibernate 5.0.5 (HHH-10309)