gnodet opened a new pull request, #26534: URL: https://github.com/apache/camel/pull/26534
## Summary Bump Scalpel `extension3` from 0.4.0 to 0.4.2 and leverage new report fields introduced in the 0.4.x series to improve the shadow comparison section of PR comments. ### What changes **Scalpel 0.4.0 → 0.4.2** (`.mvn/extensions.xml`) - 0.4.1: fixes `buildAllIfNoChanges` handling, adds `reactorModuleCount` report field, emits decision inputs, fixes non-reactor file cascade to root module - 0.4.2: fixes NPE when Scalpel trims reactor to empty (`currentProject` restore after `setProjects([])`) **Explain mode** (`-Dscalpel.explain=true`) Each affected module now carries an `evidence[]` array in the report naming the exact file, property, managed dependency, or graph edge that caused it to be included. The PR comment surfaces this inline per module — e.g.: ``` - `camel-kafka` ← properties/version.kafka - `camel-aws2-s3` ← managedDependencies/software.amazon.awssdk:s3 ``` **N-of-M framing** using `reactorModuleCount` (0.4.1+ report field) The shadow summary line now reads _"47 of 1,847 tested"_ instead of a bare count, without extra shell arithmetic — the reactor size comes directly from the report. **`testedModulesCount`** (0.4.x report field) Eliminates the manual `grep -c` counting of the `scalpel_would_test` comma-separated list. Falls back to counting `affectedModules` entries when the field is absent (older report schema). **PR comment layout** POM change details (changed properties / managed deps / managed plugins) are now shown _above_ the per-module lists, giving reviewers the "why" before the "what". ### Relation to #24579 PR #24579 removes the grep layer entirely, making Scalpel the sole detection mechanism. This PR is a prerequisite — it improves what the shadow section shows while the dual-detection architecture is still in place, so the evidence and N-of-M data are visible during the validation period. -- 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]
