[
https://issues.apache.org/jira/browse/SUREFIRE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154503#comment-17154503
]
Falko Modler commented on SUREFIRE-1068:
----------------------------------------
Another workaround (double dollar):
{code:xml}
<surefire.forkNumber>$${surefire.forkNumber}</surefire.forkNumber>
{code}
But watch out: IntelliJ will then pass {{-Dsurefire.forkNumber=$1}} to mvn.
> forkNumber in systemPropertyVariables requires prefix
> -----------------------------------------------------
>
> Key: SUREFIRE-1068
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1068
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.16
> Reporter: Eric Pederson
> Assignee: Tibor Digana
> Priority: Minor
> Fix For: 3.0
>
>
> 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).
> {code:xml}
> <systemPropertyVariables>
> <surefire.forkNumber>${surefire.forkNumber}</surefire.forkNumber>
> </systemPropertyVariables>
> {code}
> But this does:
> {code:xml}
> <systemPropertyVariables>
> <surefire.forkNumber>0${surefire.forkNumber}</surefire.forkNumber>
> </systemPropertyVariables>
> {code}
> (note the leading *0*)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
