Join GitHub today
3.5.0 and new strict mode: java.lang.IllegalStateException: No entity type for ... #972
I hit a problem with the processor phase due to the new strictMode behavior: we have a class which isn't annotated with a JPA annotation in our hierarchy and we now have:
Thanks for your feedback!
The error is non-intentional in this case, it should have been just skipped. Could you provide the stacktrace?
strictMode should not be an open configuration flag, but set on the specific AnnotationProcessor. In the JPA case, properties of non-annotated superclasses are now ignored.
Here it is: