apache / apache/maven-project-info-reports-plugin
[MPIR-458] Replace maven-dependency-tree with Maven Resolver
- Dominant language
- Java
- Stars
- 29
- Forks
- 41
- Avg merge
- 4h 17m
- Merged PRs (30d)
- 3
Description
**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MPIR-458](https://issues.apache.org/jira/browse/MPIR-458?redirect=false)** and commented
As depicted by [cstamas](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas) maven-dependency-tree is an obsolete component these days, we should replace its usage with Maven Resolver directly.
---
**Affects:** 3.5.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the project's uses of maven-dependency-tree and reviewing how they obtain dependency information. Compare those entry points with the Maven Resolver APIs, then verify that the affected reports still produce equivalent dependency results after the replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100