[MRELEASE-1101] Completely revise argument(s) handling
- Dominant language
- Java
- Stars
- 128
- Forks
- 145
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MRELEASE-1101](https://issues.apache.org/jira/browse/MRELEASE-1101?redirect=false)** and commented
Currently, we have multiple parameters which accept goals, args, options, etc. They suffer from several problems:
* They accept everything and don't reject. E.g., goals should accepts goals only which is not the case.
* It accepts one arg line and internally parses it.
Both is wrong:
* We need exactly **one** config element `` which take everything what forked Maven shall receive
* We do double, brittle parsing. It must be one arg at a time, therefore a single string must be rather a array/list of args.
---
**Affects:** 3.0.0-M6
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing the plugin parameters that accept goals, arguments, and options, then follow how arguments reach the forked Maven invocation. Done means one configuration supplies a list of individual arguments without additional parsing or accepting unrelated values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100