Content module without a dedicated IntelliJ IDEA module
Checks that all content modules registered in a plugin descriptor have dedicated IntelliJ IDEA modules.
The way to register a content module using moduleName/subDescriptorName syntax without extracting a separate IntelliJ IDEA module for it is deprecated now. Each content module should have its own IntelliJ IDEA module to allow checking that dependencies used during compilation are available at runtime.
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.
ContentModuleWithoutDedicatedJpsModule- 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: ContentModuleWithoutDedicatedJpsModule
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: |