jamesnetherton opened a new pull request, #9491: URL: https://github.com/apache/camel-quarkus/pull/9491
`IncrementalBuildMojo` had no tests. This adds unit tests that run the mojo against a temporary project tree and a synthetic Scalpel report, then assert on the output JSON. They cover: * Full build fallbacks (incremental disabled, missing report, Scalpel full build trigger, no affected modules, BOM only changes) * Mapping affected modules to native test modules, including categories, nested paths and `<group>-grouped` modules * Native test matrix distribution and the max size check * Functional test scope and modules * JVM-only tests and `runExamples` * Modules consuming other modules' sources via `copy-tests.source.dir` / `group-tests.source.dir` * Container image property detection in test modules, grouped modules and `integration-tests-support` dependents The tests uncovered three issues, fixed here: * JVM-only modules affected by a container image change were dropped when the Scalpel report listed no affected modules * Container image references under `integration-test-groups/` always mapped to a native `<group>-grouped` module. They are now resolved via the declared `group-tests.source.dir`, so JVM groups such as `xml/jvm` are routed to the JVM list * `UPSTREAM` modules under `integration-tests-jvm/` were scheduled for testing, unlike their native counterparts 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
