[3.10] Consider user wide properties too
Open
enhancement
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
### New feature, improvement proposal
This is just a faint idea, as 3.10 is wildly different than 4.0 regarding properties, and this may introduce feature disparity, like user-wide maven.config, where 4.0 would use maven.properties?
All in all, goals:
* be able to define user wide properties
* do not break feature parity, if possible
Contributor guide
Research direction
Start by comparing how Maven 3.10 and 4.0 currently handle properties, with particular attention to the stated maven.config and maven.properties disparity. Done means defining a user-wide property mechanism while preserving feature parity where possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100