apache / apache/maven-surefire
[SUREFIRE-1068] forkNumber in systemPropertyVariables requires prefix
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Eric Pederson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ericacm)** opened **[SUREFIRE-1068](https://issues.apache.org/jira/browse/SUREFIRE-1068?redirect=false)** and commented
The `${surefire.forkNumber}` placeholder cannot be used alone in a `systemPropertyVariable`. The workaround is to prefix the value.
For example, this doesn't work (the `surefire.forkNumber` system property does not exist when running the test).
```xml
${surefire.forkNumber}
```
But this does:
```xml
0${surefire.forkNumber}
```
(note the leading **0**)
---
**Affects:** 2.16
1 votes, 6 watchers
Contributor guide
Research direction
Start by reproducing the two systemPropertyVariables examples described in the issue against Surefire 2.16, comparing the placeholder-only value with the prefixed value. Trace how surefire.forkNumber is resolved and passed into test system properties; done means the placeholder-only form creates the expected system property without requiring a prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100