Troubleshooting

For Maven and Gradle projects, Qodana uses the following directories to access third-party libraries:

Mounting these directories saves Qodana from downloading all dependencies again while using these linters:

• Qodana for JVM

• Qodana Community for JVM

• Qodana Community for Android

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, check pom.xml for Maven or the build.gradle file for Gradle configurations.

• In the /data/results/ directory, each inspection that detected a possible problem creates its own file named ID.json, where ID is the inspection name that can be used in qodana.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.

A typical project structure can have a directory structure similar to this:

repo/
   .git/
   project/
   ...

Here, the repo/.git directory contains information that should be accessible by Qodana, and the repo/project directory contains the project that needs to be inspected by Qodana.

In this case, you can mount the repo root directory using the -v Docker option, and tell Qodana to only scan the repo/project directory using the --project-dir= Qodana option:

$
docker run \
  -v repo/:/data/project/ \
  jetbrains/qodana-<linter> \
--project-dir=/data/project/project/

During inspections, Qodana may report about missing files, packages, modules, or classes. In this case, you need to have your project prepared for code inspection. For example, you can create a script and configure Qodana for running it as shown in the Prepare your project section.