agoffer commented on issue #13430: URL: https://github.com/apache/maven/issues/13430#issuecomment-6251077889
**Second real-world reproducer, same root cause as Resolver [#2208](https://github.com/apache/maven-resolver/pull/2208) as far as I can tell** Affected: Maven 3.10.0 (Resolver 2.0.24). Not affected: Maven 3.9.16. Our project declares `com.google.guava:guava:33.5.0-jre` directly. A dependency’s published POM declares Guava as `[15, 32)` (runtime scope). On 3.10.0, `dependency:tree -Dverbose` shows 33.5.0-jre as “omitted for conflict with 31.1-jre”, and 31.1-jre has no children (failureaccess, checker-qual and so on are missing). On 3.9 the same version is selected, with all its children. The build succeeds, and we found the problem as a runtime failure after a deployment. On 3.10.0 the children come back with `-Daether.dependencyCollector.bf.skipper=false`, with `=versioned`, or with `-Daether.dependencyCollector.impl=df`. Only the default (versionless) loses them. In a CI log we also saw the POMs of 85 in-range Guava versions fetched, but none of their dependencies. This matches the root cause in [#2208](https://github.com/apache/maven-resolver/pull/2208). Workaround that works for us: pin the version in `dependencyManagement`. -- 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]
