You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 940e6b7
Browse filesBrowse the repository at this point in the historyBrowse files
* Start fix for #1809
Assisted-by: Claude Code:claude-opus-5-5
* Treat Maven 4 implicit subprojects as a reactor
A Maven 4 root (model 4.1.0, pom packaging, no <subprojects> list)
builds every direct subdirectory holding a pom.xml. Only the vendored
planner knew this. Hosted scan pinned just the root pom while a
module kept its own version, VEX attested that pin as not_affected,
the sbt ambiguity guard let such a root through, and the project
scope of the Maven cache skipped the modules' dependencies.
Every caller now asks one maven_reactor predicate that follows the
planner's own discovery rule, including the discoverSubprojects
opt-out in .mvn/maven.config. The hosted engine reads each
subdirectory's pom.xml beside such a root so the rewriter can refuse
it as a reactor.
Fixes#1809
Assisted-by: Claude Code:claude-opus-5-5
* Share one subproject probe; skip refused pins
Review follow-ups for the Maven 4 reactor fix. The hosted engine,
VEX and the Maven cache scope now find discovered subprojects
through the planner's own probe, so a .git directory or a directory
named pom.xml never makes a root a reactor in one place but not
another.
A refused reactor root pins nothing, so the hosted confirmation
probe no longer counts a suffixed version an older release left in
it, or one a module pom names, as a redirected dependency. The CLI
contract now describes Maven 4 discovered reactors.
Refs #1809
Assisted-by: Claude Code:claude-opus-5-5
---------
Co-authored-by: Claude <noreply@anthropic.com>
"pom.xml declares <modules>/<subprojects>; hosted mode reads only the root pom, so a module's own <version> of {} would stay unpatched. pom.xml and .mvn/ were left as they are and the dep is not counted as redirected; use `scan --mode vendored`, which pins each module's declaration",
8676
+
"pom.xml heads a multi-module reactor (<modules>/<subprojects>, or Maven 4 subproject discovery); hosted mode reads only the root pom, so a module's own <version> of {} would stay unpatched. pom.xml and .mvn/ were left as they are and the dep is not counted as redirected; use `scan --mode vendored`, which pins each module's declaration",
let dep = "<dependencies>\n <dependency>\n <groupId>org.slf4j</groupId>\n <artifactId>slf4j-api</artifactId>\n <version>1.7.36</version>\n </dependency>\n </dependencies>\n";
0 commit comments