Class loaded from a different dependency at runtime
Reports class references that will resolve to a different class at runtime than at compile time.
Example: MainModule ├── DepModule │ └── Av1.jar ← my.example.A (will be used at runtime!) └── Av2.jar ← my.example.A (used at compile time) The IDE resolves A from Av2, but the JVM loads it from Av1. Calling a method that exists only in Av2 causes NoSuchMethodError.
Fix: move Av2 before DepModule so both compile and runtime use the same class.
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
ClassOverriddenAtRuntime- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Inspection ID: ClassOverriddenAtRuntime
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |