apache / apache/maven-dependency-tree
Deprecate this project
- Dominant language
- Java
- Stars
- 27
- Forks
- 31
- Avg merge
- 5h 53m
- Merged PRs (30d)
- 1
Description
### New feature, improvement proposal
The idea behind this project was to unify APIs (between maven2 and 3? or between org.sonatype and org.eclipse packages of resolver?)
In reality this project just adds overhead and layer of indirection that makes move/progress nearly impossible. It nicely served its purpose long time ago, but today is just a hurdle: use Resolver 1 APIs in Maven 3 or use new Maven 4 APIs, not this.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the project’s current role and the stated Maven Resolver 1, Maven 3, and Maven 4 API relationships, then determine the deprecation scope and what migration or completion criteria would make the proposal done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100