Hi everyone, Maven Dependency Tree builds a project's dependency graph, including the verbose graph with conflict losers and pre-managed versions, by wrapping Maven Resolver. Resolver now exposes all of that directly, so the wrapper no longer adds value.
Its last two Maven consumers have moved off it: - maven-dependency-plugin: (MDEP-969, https://github.com/apache/maven-dependency-plugin/pull/1712) - maven-project-info-reports-plugin: (MPIR-458, https://github.com/apache/maven-project-info-reports-plugin/pull/670) Both changes are merged and will ship in dependency-plugin 3.12.0 and project-info-reports 3.10.0. No other Apache Maven component depends on it. Outside Maven, a GitHub code search of default branches finds usage in Camel, camel-kafka-connector, camel-spring-boot, Felix maven-bundle-plugin, NetBeans, NiFi Maven, PLC4X, IoTDB, iotdb-extras, TsFile, and Meecrowave. Retiring it will not break these projects: version 3.3.0 will remain on Maven Central, and https://github.com/apache/maven-dependency-tree/issues/150 describes how to call Resolver directly instead. While the git history shows 31 commits since 3.3.0 (May 2024)—including 21 this year—9 of those are Dependabot commits, reflecting routine maintenance rather than new feature development. I therefore propose that we retire maven-dependency-tree. If this vote passes, I will make one final release, explicitly noting the retirement on the component site, and then archive the source code repository (making it read-only). The component retirement process is detailed here: https://maven.apache.org/developers/retirement-plan-plugins.html This vote will remain open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... Best regards, Sylwester
