slachiewicz opened a new issue, #150: URL: https://github.com/apache/maven-dependency-tree/issues/150
maven-dependency-tree wraps Maven Resolver to build a project's dependency graph, including the verbose graph with conflict losers and pre-managed versions. Resolver exposes all of this directly, and [MPIR-458](https://github.com/apache/maven-project-info-reports-plugin/issues/308) and [MDEP-969](https://github.com/apache/maven-dependency-plugin/issues/1479) already ask to drop the wrapper. This component is planned for retirement once its Maven consumers no longer need it. The plan has four steps: 1. Move the two Maven consumers to Resolver: maven-dependency-plugin (MDEP-969) and maven-project-info-reports-plugin (MPIR-458). 2. Hold the retirement vote on [email protected]. 3. Cut a final release marked `(RETIRED)`. 4. Archive this repository. Version 3.3.0 stays on Maven Central. To migrate, call Resolver directly: - For the graph Maven itself resolves, use `ProjectDependenciesResolver` from maven-core and read `DependencyResolutionResult.getDependencyGraph()`. - For the verbose graph, call `RepositorySystem.collectDependencies` with a session that sets `ConflictResolver.CONFIG_PROP_VERBOSE` and `DependencyManagerUtils.CONFIG_PROP_VERBOSE` to `true`. - In Maven 4 plugins, use `org.apache.maven.api.services.DependencyResolver`. Other Apache projects that still depend on it, from a GitHub code search of default branches: Camel, camel-kafka-connector, camel-spring-boot, Felix maven-bundle-plugin, NetBeans, NiFi Maven, PLC4X, IoTDB, iotdb-extras, TsFile, and Meecrowave. -- 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]
