Troubleshooting
This section contains information that can help you troubleshoot common problems.
List of Docker image paths
Path | Description |
---|---|
| Root directory of the project to be analyzed |
| Directory to store the analysis results |
| Directory containing the IDE distribution |
| Directory where the IDE contains configuration |
| Used if a profile was not previously configured either via the CLI or the |
For Maven and Gradle projects, Qodana uses the following directories to access third-party libraries:
Path | Description |
---|---|
| Maven project dependencies |
| Gradle project dependencies |
Mounting these directories saves Qodana from downloading all dependencies again while using these linters:
List of files for investigating Qodana behavior
There are several options for examining Qodana behavior using the /data/results
directory:
The
/data/results/projectStructure/Modules.json
file lists all modules detected by Qodana. It should be identical to the list that you expect to see while opening the project in IDEA. If it is not the case, checkpom.xml
for Maven or thebuild.gradle
file for Gradle configurations.In the
/data/results/
directory, each inspection that detected a possible problem creates its own file namedID.json
, whereID
is the inspection name that can be used inqodana.yaml
for including or excluding inspections. You can find the complete list of inspection IDs in the/data/results/.descriptions.json
file using the/groups/*/inspections/*/shortName
pattern.In
/data/results/log/idea.log
, you can investigate suspicious warnings.