GeezerVison

Maven's conflict resolution can retain a dependency under a test or
provided parent while its effective scope is compile. The Maven facts
extension split each module's merged graph into prod and dev roots by
that effective scope and then dropped edges crossing the split, stranding
the node in a root with no parent edge. The manifest consumer reported
those nodes as orphaned components not reachable from any direct
dependency.

Assign root membership by reachability from each scope's direct
dependencies instead: a node reached from a compile/runtime/system
direct dependency stays in the prod root, and one reached only through a
test/provided parent lands in the dev root with its edge intact.

Add a shared reachability assertion to the Gradle, Maven and sbt compat
smoke tests, unit-tested over synthetic records, and cover the scope
conflict in the Maven fixture.

cursor Bot left a comment