Codeac Auto-Include: Will All Maven Modules Be Validated?

Answer

No. The --auto-include flag does **not** guarantee that every Maven module will be validated when Codeac runs with restricted file‑system access. If a module directory cannot be read, Codeac silently skips it during auto‑include.

Likely Explanation

Codeac builds its analysis scope by querying Maven’s reactor (the list of modules that mvn would build). It then attempts to read each module’s pom.xml and source files. When the process lacks read permission for a module’s directory, the file‑system call fails, Codeac treats the module as unavailable, and it is omitted from the analysis without emitting an error by default.

Confirmed Facts

1. Auto‑include relies on Maven’s reactor to discover modules; only modules present in the reactor are considered.
2. Modules listed in the parent POM’s <modules> section are included unless they have <skip>true</skip> or are excluded by an active Maven profile.
3. If a module is not in the reactor (e.g., missing from <modules>) or is marked as skipped, Codeac will not validate it.
4. Setting CODEAC_SKIP_DUPLICATES=true changes duplicate‑detection logic: duplicate annotations are ignored rather than reported, which can mask errors that would appear locally.

Steps to Verify What Is Being Validated

1. Inspect the parent POM for module list:

   grep -A 20 '<modules>' pom.xml

2. Check for skips or profile exclusions:

   mvn help:effective-pom | grep -A 5 -B 5 '<skip>'

3. Run Codeac with verbose logging to see which modules are processed:

   codeac --verbose analyze

   Look for lines like Processing module: my-module or warnings about inaccessible directories.
4. In CI, compare the list of modules Codeac reports with the reactor list from

   mvn help:evaluate -Dexpression=reactorProjects -q -DforceStdout

   .

Detecting Silently Skipped Modules

• Enable --verbose or --debug flags; Codeac will log "Skipping module X due to insufficient permissions" when it cannot read a directory.
• Check the exit code: a non‑zero code often indicates that some modules were skipped, but you must pair it with verbose output to confirm.
• If you have access to the CI workspace, run

  find . -type d -name '*' -exec test -r {} \\; -print

  to verify readability of each module directory.

Impact of CODEAC_SKIP_DUPLICATES=true

When this environment variable is set to true, Codeac’s duplicate‑annotation detector treats subsequent occurrences as non‑errors and does not report them. This can hide genuine duplicate‑annotation problems that would be surfaced locally where the variable is unset or false. To avoid masking, either unset the variable in CI or run a separate analysis pass with it disabled to verify duplicate detection.

Missing Diagnostic Detail (only needed if it changes the recommendation)

Can you confirm whether the CI runner has read access to **all** module directories? If any directory is unreadable, the auto‑include flag will skip those modules, and you must adjust permissions or explicitly list the modules in the configuration.