You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@codehaus.org> on 2015/02/01 01:02:18 UTC

[jira] (SUREFIRE-1136) Current working directory propagation in forked mode

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

Tibor Digana commented on SUREFIRE-1136:
----------------------------------------

commit	2b4629c71e5c82716d99a738f02063c90413253f

> 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)