Cannot access content module dependency
Reports violations of content module visibility when declaring module dependencies.
Content modules can specify their visibility as private (default, when missing), internal, or public.
When declaring dependencies on other modules, the following rules must be followed:
Private modules can only be accessed within the same plugin.
Internal modules can only be accessed when declared within the same namespace (
content@namespace).Public modules can be accessed from anywhere.
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.
ContentModuleVisibility- 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: ContentModuleVisibility
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: |