Inspection results mismatch in IntelliJ IDEA vs. inspectCode CLI
0 reputation · 14 Sept 2026, 10:15 UTC
When running code inspections locally in IntelliJ IDEA, the output often differs from the results produced by the standalone inspectCode command‑line tool. The local IDE uses the project’s .idea configuration and the current inspection profile, while the CLI relies on the supplied config.xml and the environment’s classpath. This inconsistency can lead to false positives or missed warnings in continuous‑integration pipelines.
The goal is to achieve a deterministic, environment‑agnostic inspection outcome. However, the following uncertainties remain:
- Do the IDE and CLI resolve inspection profiles identically when the same profile file is used?
- Is there a difference in plugin or language‑support version handling between the two executables?
- How does the classpath resolution affect which inspections are applied, especially for projects with multiple modules?
What specific factors cause the discrepancy in inspection results between the local IDE and the inspectCode CLI tool, and how can they be aligned for consistent CI/CD validation?
jetbrains