slachiewicz opened a new pull request, #147: URL: https://github.com/apache/maven-dependency-tree/pull/147
Adds per-major expected trees to the `verbose`, `verbose-war`, `display-optional-information` and `maven-version` ITs and removes the Maven 4 matrix exclusion from #145. Maven 4 collects with `TransitiveDependencyManager` (`maven.resolver.dependencyManagerTransitivity`, default `true`), which also applies the `dependencyManagement` of transitive POMs; Maven 3's `ClassicDependencyManager` applies only the project's own. In these fixtures `maven-project:2.0.6` manages `classworlds 1.1` and `plexus-utils 1.4.1`, so under Maven 4 `classworlds` resolves to `1.1` instead of `1.1-alpha-2` and every node below depth 1 carries a "version managed from" annotation. The non-verbose trees, built through Maven's own `ProjectDependenciesResolver`, shift the same way, so the verbose tree matches the classpath Maven 4 actually builds; pinning the classic manager in `DefaultDependencyCollectorBuilder` would make it disagree with that classpath. maven-dependency-plugin's `tree-verbose` IT already carries the same `expected-v4.txt`. The `maven-version` script is the BeanShell text under its new `.groovy` name; it is rewritten in Groovy here because it needs the `mavenVersion` binding. Stacked on #145. Fixes #146. Verified: `mvn -Prun-its verify` with `-Dinvoker.mavenHome` set to 3.9.16, 3.10.0-rc-1 and 4.0.0-rc-6 → 10/10 ITs pass on each; `spotless:check` and `apache-rat:check` pass. -- 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]
