apache / apache/maven-dependency-plugin
[MDEP-969] Use resolver api in dependency:tree
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** opened **[MDEP-969](https://issues.apache.org/jira/browse/MDEP-969?redirect=false)** and commented
We should direct use resolver api in dependency:tree instead of external library
---
No further details from [MDEP-969](https://issues.apache.org/jira/browse/MDEP-969?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the dependency:tree goal and trace how it currently obtains dependency information. Identify the external library and the Maven Resolver API usage involved, then compare existing tests for dependency:tree. Done means the goal uses the resolver API directly and its behavior remains covered by the relevant tests.
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
- 25/100