Reports class references that resolve to a different class at runtime than at compile time.

This happens when several dependencies provide the same fully qualified name, and the compile and runtime classpaths pick different ones. It may cause NoSuchMethodError, NoSuchFieldError, or other unexpected runtime behavior.

Example:

  MainModule
  ├── DepModule
  │   └── Av1.jar  ← my.example.A (loaded at runtime)
  └── Av2.jar      ← my.example.A (used at compile time)

The IDE resolves A from Av2, but the JVM loads it from Av1.

How to fix: depending on the case, reorder the dependencies (for example, move Av2 before DepModule), remove one of them, or make the transitive dependency exported.

Works only for the IntelliJ (JPS) project model.

New in 2026.3