apache / apache/maven-compiler-plugin
[MCOMPILER-580] Remove all properties overlapping with args
- Dominant language
- Java
- Stars
- 261
- Forks
- 191
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 8
Description
**[Romain Manni-Bucau](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romain.manni-bucau)** opened **[MCOMPILER-580](https://issues.apache.org/jira/browse/MCOMPILER-580?redirect=false)** and commented
We tend to have duplicated compiler options as properties but we don't validate the presence in both leading to broken setups if user prefer to use args for consistency (evertything configured at the same location rather than spread accross levels).
Goal of this ticket is to revisit that for v4.0.0 and drop all custom properties to 100% leverage the compilerArgs only.
---
No further details from [MCOMPILER-580](https://issues.apache.org/jira/browse/MCOMPILER-580?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the compiler option properties and the compilerArgs configuration described in the issue. Identify every custom property that overlaps with compiler arguments, then determine the complete set that must be removed for the v4.0.0 goal of relying entirely on compilerArgs. Done means duplicated custom properties no longer remain and compiler options are consistently configured through compilerArgs.
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
- Mostly clear
- Newbie friendliness
- 25/100