gnodet opened a new pull request, #26832: URL: https://github.com/apache/camel/pull/26832
## Summary The standalone `Dependency Analysis` workflow (`dep-check.yml`) duplicated the full reactor build on every PR: checkout, JDK setup, SNAPSHOT plugin install, stub install, full compile, *then* pilot:dependencies. That burned an entire extra CI runner slot for a non-blocking, informational check. ## Change - Remove `dep-check.yml` - Add two steps (**Run dependency analysis** + **Upload dependency analysis report**) at the end of the JDK 25 matrix entry in the `Build and test` workflow - The `regen.sh` step that already runs earlier in the same job compiles the full reactor and installs all JARs into the local `.m2` repository — `pilot:dependencies` reuses those compiled classes directly, with **zero recompilation** - The `EXCLUDED_MODULES` list is hoisted to a job-level `env` variable (`DEP_CHECK_EXCLUDED_MODULES`) so it lives in a single place ## Why JDK 25 (not 17) The matrix has JDK 17 (runtime compat) and JDK 25 (primary). Pilot requires JDK 21+, so JDK 25 is the only valid target — and it's the primary build anyway. ## Non-goals The analysis remains `continue-on-error: true` — no change in blocking behaviour. The `Dependency Review` workflow (`depsreview.yaml`, job `dependency-review`) is unrelated: it runs `actions/dependency-review-action`, a GitHub-provided action that scans the dependency graph *diff* of a PR for known vulnerabilities (CVEs) using the GitHub Advisory Database. No compilation involved. It stays as-is. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
