[MNG-8758] CLAPP
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MNG-8758](https://issues.apache.org/jira/browse/MNG-8758?redirect=false)** and commented
We modified CLI way of working, and we opened up Maven to contain multiple CLI tools by (almost) fully reusing the CLI infra we have, hence today we have aside of existing `mvn` CLI tools like `{}mvnenc{`}, `mvnsh` and upcoming `mvnup` and so on.
Problem with these "extra tools" is that they (along with their dependencies) have to reside in Maven Core `/lib` directory. The tools like `mvnenc` and `mvnsh` had "luck" that all they need (plexus sec dispatcher and JLine) are already in core, but any new tool we'd like to add, may need dependencies not present in `{}/lib{`}, potentially bloating it.
Proposal: Maven CLAPP – like "Maven Command Line App".
---
No further details from [MNG-8758](https://issues.apache.org/jira/browse/MNG-8758?redirect=false)
Contributor guide
Research direction
Start with the MNG-8758 proposal and inspect Maven Core's /lib directory plus the existing mvnenc and mvnsh CLI tools. Determine how a CLAPP could let extra tools keep their dependencies out of core; done requires an agreed design and implementation scope for the proposed CLI approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100