Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from maven-dependency-tree to direct use of Resolver API #511

Open
basil opened this issue Jun 30, 2023 · 0 comments
Open

Migrate from maven-dependency-tree to direct use of Resolver API #511

basil opened this issue Jun 30, 2023 · 0 comments
Labels

Comments

@basil
Copy link
Member

basil commented Jun 30, 2023

Tamás Cservenák recommends we get rid of org.apache.maven.shared.dependency.graph.DependencyGraphBuilder (maven-dependency-tree). While not officially deprecated (yet), this suffers from same issues as all other legacy/maven2 things (e.g., maven-artifact-transfer), (mis)uses project building request everywhere, uses deprecated classes (e.g., ArtifactRepository), etc.

The suggestion is to replace this with direct usages of the Resolver API. For examples:

https://github.com/apache/maven-resolver/tree/master/maven-resolver-demos/maven-resolver-demo-snippets/src/main/java/org/apache/maven/resolver/examples

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant