[
https://jira.codehaus.org/browse/SUREFIRE-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362199#comment-362199
]
Norbert Wnuk commented on SUREFIRE-1136:
----------------------------------------
Known limitation: $\{surefire.forkNumber\} propagation is not supported on
Maven 2.x, the variable will be resolved to 'null' value all the time -
https://github.com/apache/maven-surefire/pull/84
> Current working directory propagation in forked mode
> ----------------------------------------------------
>
> Key: SUREFIRE-1136
> URL: https://jira.codehaus.org/browse/SUREFIRE-1136
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.18.1
> Reporter: Norbert Wnuk
> Assignee: Andreas Gudian
> Priority: Minor
> Fix For: 2.19
>
>
> Surefire plugin does not resolve surefire.forkNumber variable for working
> directory so that the same invalid directory is set for all forked JVMs. The
> same time user.dir property is propagated properly which leads to
> inconsistent behavior in JDK API -
> http://stackoverflow.com/questions/1234795/why-is-the-user-dir-system-property-working-in-java
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
