ci: add Scalpel POM dependency detection using released 0.1.0#22510
Merged
gnodet merged 1 commit intoapache:mainfrom Apr 9, 2026
Merged
ci: add Scalpel POM dependency detection using released 0.1.0#22510gnodet merged 1 commit intoapache:mainfrom
gnodet merged 1 commit intoapache:mainfrom
Conversation
Add Maveniverse Scalpel as a parallel POM dependency detection mechanism in the incremental build script. Scalpel compares effective POM models between the base branch and the PR, catching managed dependencies, plugin version changes, BOM imports, and transitive dependency impacts that the existing grep-based approach misses. Since Scalpel 0.1.0 is released to Maven Central, add it permanently to .mvn/extensions.xml. On developer machines it is a no-op (no base branch env vars detected). This avoids the complexity of temporary extension injection and snapshot repository configuration. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
5 tasks
Contributor
|
ℹ️ CI did not run targeted module tests. |
oscerd
approved these changes
Apr 9, 2026
gnodet
force-pushed
the
worktree-scalpel-release
branch
2 times, most recently
from
599b0f0 to
b40772d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.mvn/extensions.xmlincremental-build.shalongside the existing grep approachGITHUB_BASE_REF→ no base branch → returns immediately)Why
The grep-based approach has 5 structural limitations. For example, when Dependabot bumps
azure-sdk-bom-version(#21744), grep finds onlycamel-azure/pom.xmlbut misses all 12 child Azure modules that inherit via the BOM. Scalpel catches them via effective POM model comparison.How it works
Scalpel is a Maven core extension that compares effective POM models between the base branch and the PR. In CI:
incremental-build.shrunsmvn validate -Dscalpel.mode=report(~60-90s, no compilation)target/scalpel-report.jsonwith affected modules and reasons-Dscalpel.fullBuildTriggers=overrides the default (.mvn/**) since Scalpel lives inextensions.xmlTest plan
parent/pom.xml🤖 Generated with Claude Code
Claude Code on behalf of Guillaume Nodet