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

Problem Context

When running Codeac locally the tool automatically includes every Maven module in the analysis scope. In a production CI pipeline the same flag may cause modules to be omitted due to restricted file‑system permissions, potentially leading to missing annotation detection failures.

Constraints & Uncertainty

Codeac’s configuration file defaults to $HOME/.codeac/config.yaml locally, but CI environments look for /etc/codeac/config.yaml unless overridden. The --auto-include flag is enabled by default, yet its behavior when the tool cannot read certain module directories is not documented. Additionally, the environment variable CODEAC_SKIP_DUPLICATES is often set to true in CI, altering duplicate detection logic.

Key Questions

• Does the --auto-include flag guarantee that every Maven module is validated for missing annotations when the tool runs under restricted file‑system access?
• Which conditions cause Codeac to silently skip modules during auto‑include in CI, and how can users detect this?
• Can setting CODEAC_SKIP_DUPLICATES=true in CI unintentionally mask duplicate annotation errors that would otherwise surface locally?