dependabot[bot] opened a new pull request, #9450: URL: https://github.com/apache/camel-quarkus/pull/9450
Bumps [eu.maveniverse.maven.scalpel:extension](https://github.com/maveniverse/scalpel) from 0.4.3 to 0.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/maveniverse/scalpel/releases";>eu.maveniverse.maven.scalpel:extension's releases</a>.</em></p> <blockquote> <h2>Scalpel 0.5.0</h2> <p>fix: unmapped root-level files always trigger a full build (<a href="https://redirect.github.com/maveniverse/scalpel/issues/229";>#229</a>) (<a href="https://redirect.github.com/maveniverse/scalpel/issues/234";>#234</a>)</p> <ul> <li>fix: unmapped root-level files always trigger a full build (<a href="https://redirect.github.com/maveniverse/scalpel/issues/229";>#229</a>)</li> </ul> <p>Bare root-level files (e.g. settings.properties, lombok.config) sit outside every module's directory tree, so ModuleMapper.findOwningModule returns null for them. When such a file was the <em>only</em> change, the 'no modules affected' gate naturally produced a full build (reactor untouched in trim mode). But when combined with <em>other</em> module changes, the unmapped file was silently dropped: only the changed module built, ignoring the root-level change entirely.</p> <p>Root cause: ModuleMapper discarded unmapped files with no trace. ScalpelLifecycleParticipant never saw them and could not act on them.</p> <p>Fix:</p> <ul> <li>ModuleMapper.Result gains getUnmappedFiles(): files for which findOwningModule returned null.</li> <li>ScalpelLifecycleParticipant checks unmappedFiles immediately after source mapping. A non-empty set triggers the same full-build path as fullBuildTriggers: early return without trimming the reactor. In report/shadow mode a full-build report is written.</li> </ul> <p>This makes the implementation match the documented behaviour: 'Files at the repository root that are not part of any module are treated as triggering a full build.'</p> <p>Tests:</p> <ul> <li>ModuleMapperTest: verify unmappedFiles populated for bare root files, and alongside module changes.</li> <li>ScalpelLifecycleParticipantTest: trim-mode alone, trim-mode mixed with module change, and skip-tests-mode all trigger full build.</li> <li>IT unmapped-root-file: end-to-end regression test.</li> </ul> <p>Closes <a href="https://redirect.github.com/maveniverse/scalpel/issues/229";>#229</a></p> <p>Co-authored-by: Claude Sonnet 4.6 <a href="mailto:[email protected]";>[email protected]</a></p> <ul> <li>fix: update ITs broken by unmapped-root-file change</li> </ul> <ul> <li>shadow-unaffected: notes.md is now correctly a full-build trigger (root-level file not owned by any module); update verify.groovy to accept either exit path while still asserting the stale shadow doc is overwritten and history is not appended.</li> <li>uncommitted: build.log is written by the invoker to the working tree before Maven runs; with scalpel.uncommitted=true it appears as an untracked root-level file and now triggers a full build. Exclude it via scalpel.excludePaths=build.log so the test exercises the module-b uncommitted-source path it was designed for.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/maveniverse/scalpel/commit/dc4fcf24b316f96b26acc797b9315cbd4fef362a";><code>dc4fcf2</code></a> fix: unmapped root-level files always trigger a full build (<a href="https://redirect.github.com/maveniverse/scalpel/issues/229";>#229</a>) (<a href="https://redirect.github.com/maveniverse/scalpel/issues/234";>#234</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/5f6cb5896967ef1ece685f560c6655ed793ff72a";><code>5f6cb58</code></a> fix: treat test-only POM dep changes as test-only affected (<a href="https://redirect.github.com/maveniverse/scalpel/issues/220";>#220</a>) (<a href="https://redirect.github.com/maveniverse/scalpel/issues/238";>#238</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/44e1ac2b3d28683c5dffa9b241e3e0c06220a23f";><code>44e1ac2</code></a> Fix formatting of scalpel.excludeChanges entry</li> <li><a href="https://github.com/maveniverse/scalpel/commit/0074b8addfd6776cf0e35a75d4edea6098c2b447";><code>0074b8a</code></a> fix: detect pluginManagement config-only changes and propagate to children (#...</li> <li><a href="https://github.com/maveniverse/scalpel/commit/4b77319193ad1ce72024a3e8fb2aae09caea2306";><code>4b77319</code></a> chore(deps): bump eu.maveniverse.maven.shared:extension (<a href="https://redirect.github.com/maveniverse/scalpel/issues/239";>#239</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/a6310720efeabe6f370013e8758f3b18ee0f00a4";><code>a631072</code></a> chore(deps): bump org.jacoco:jacoco-maven-plugin from 0.8.15 to 0.8.16 (<a href="https://redirect.github.com/maveniverse/scalpel/issues/237";>#237</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/1ca5a8a835daecfbd840fbd4f7d0d808dee46387";><code>1ca5a8a</code></a> chore(deps): bump org.eclipse.sisu:org.eclipse.sisu.plexus (<a href="https://redirect.github.com/maveniverse/scalpel/issues/235";>#235</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/1a6d5fb18bda89c93b286147904f3a8ddc8507a7";><code>1a6d5fb</code></a> chore(deps): bump org.codehaus.plexus:plexus-classworlds (<a href="https://redirect.github.com/maveniverse/scalpel/issues/236";>#236</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/36c11b82fa1f374ba76f33ce2d079ed321284372";><code>36c11b8</code></a> fix: treat tests-classifier dependencies as test-jar consumers (<a href="https://redirect.github.com/maveniverse/scalpel/issues/231";>#231</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/32d0aa1cd65a72c3f3b573866d62139158bcfbcd";><code>32d0aa1</code></a> fix: run the analysis with the container realm as TCCL (<a href="https://redirect.github.com/maveniverse/scalpel/issues/230";>#230</a>)</li> <li>Additional commits viewable in <a href="https://github.com/maveniverse/scalpel/compare/0.4.3...0.5.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- 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]
