slachiewicz opened a new issue, #146: URL: https://github.com/apache/maven-dependency-tree/issues/146
Four ITs fail when the build runs on Maven 4.0.0-rc-6 (#145, job [ubuntu-latest jdk-21-zulu 4.0.0-rc-6](https://github.com/apache/maven-dependency-tree/actions/runs/35514612176/job/106088576933)): `verbose`, `verbose-war`, `display-optional-information`, `maven-version`. They pass on 3.9.x and 3.10.0-rc-1. The verbose tree built under Maven 4 lacks the "version managed from" annotations that come from the project's `dependencyManagement`, and it resolves the unmanaged version where the managed one is expected. Diff of the `verbose` IT, expected against Maven 4: ```diff -| | +- (org.codehaus.plexus:plexus-utils:jar:1.4.1:compile - version managed from 1.4.1; omitted for duplicate) +| | +- (org.codehaus.plexus:plexus-utils:jar:1.4.1:compile - omitted for duplicate) -| | +- org.apache.maven:maven-repository-metadata:jar:2.0.6:compile (version managed from 2.0.6) +| | +- org.apache.maven:maven-repository-metadata:jar:2.0.6:compile -| | \- (org.codehaus.plexus:plexus-utils:jar:1.4.1:compile - version managed from 1.0.4; omitted for duplicate) +| | \- (org.codehaus.plexus:plexus-utils:jar:1.0.4:compile - omitted for conflict with 1.4.1) -| \- classworlds:classworlds:jar:1.1:compile (version managed from 1.1-alpha-2) +| \- classworlds:classworlds:jar:1.1-alpha-2:compile ``` The collector runs with the dependency manager of the Maven session, and Maven 4 changed how dependency management applies to transitive dependencies (`maven.resolver.dependencyManagerTransitivity`, see [MNG-8478](https://issues.apache.org/jira/browse/MNG-8478)). Which result is right for the verbose tree, and whether `DefaultDependencyCollectorBuilder` should pin the classic manager, is the question to settle here. Until then the Maven 4 jobs are excluded from the matrix in #145. -- 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]
