maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-1068) forkNumber in systemPropertyVariables requires prefix
Date Fri, 02 Jan 2015 15:01:12 GMT

    [ https://jira.codehaus.org/browse/SUREFIRE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360540#comment-360540
] 

Tibor Digana commented on SUREFIRE-1068:
----------------------------------------

Shouldn't we mention this workaround in documentation?
I guess changing the pattern is related to major version change 3.0, hm?

> forkNumber in systemPropertyVariables requires prefix
> -----------------------------------------------------
>
>                 Key: SUREFIRE-1068
>                 URL: https://jira.codehaus.org/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
>
> 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
(v6.1.6#6162)

Mime
View raw message