apache / apache/maven-verifier
[MSHARED-1136] Deprecate verifier.forkMode in favor of maven.verifier.forkMode
- Dominant language
- Java
- Stars
- 6
- Forks
- 17
- Avg merge
- 12m
- Merged PRs (30d)
- 1
Description
**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MSHARED-1136](https://issues.apache.org/jira/browse/MSHARED-1136?redirect=false)** and commented
We should have all system properties under our namespace, thus all prefixed with `{}maven.{`}. Query `maven.verifier.forkMode` first and then fall back to `{}verifier.forkMode{`}.
---
No further details from [MSHARED-1136](https://issues.apache.org/jira/browse/MSHARED-1136?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file or test is named. Locate where the verifier reads the fork-mode system property, then inspect nearby tests for property precedence and compatibility coverage. Done means maven.verifier.forkMode is queried first, verifier.forkMode remains a fallback, and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100