apache / apache/maven-surefire
[SUREFIRE-1371] Plugin should fail if argLine is set when forkCount = 0
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** opened **[SUREFIRE-1371](https://issues.apache.org/jira/browse/SUREFIRE-1371?redirect=false)** and commented
Following up on SUREFIRE-1369: The plugin should fail with a verbose error if `forkCount=0` and `` is set.
Per [Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17), this sanity check should happen in `AbstractSurefireMojo`.
---
**Issue Links:**
- [MNG-6225](https://issues.apache.org/jira/browse/MNG-6225) Maven should warn users to use MAVEN_OPTS instead of passing system properties to mvn
Contributor guide
Research direction
Start in AbstractSurefireMojo, as the issue identifies it as the location for the sanity check. Reproduce the configuration with forkCount=0 and argLine set, then verify that the Maven Surefire plugin fails with a verbose error instead of continuing silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100