Criteria to suppress the JPA "Persistent entity missing primary key" inspection with @MappedSuperclass?


Consider the following two classes in the same module:

public class Foo {
protected Long id;
public class Bar extends Foo {

IntelliJ understands that the primary key comes from the superclass, so the inspection does not report a problem.

However, if Foo is moved to another module, the inspection reports that Bar is missing a primary key.


Could this be a bug?

1 comment

I see that you reported it in too. 

Let's continue in YouTrack. 



Please sign in to leave a comment.