[jira] [Closed] (SUREFIRE-764) java.io.tmpdir from MAVEN_OPTS should be inherited when forking

["Tibor Digana (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUREFIRE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-764.
---------------------------------
    Resolution: Not A Problem

I guess <argLine>${env.MAVEN_OPTS}</argLine> is pretty good solution instead of promising a hack in surefire 3.0.

> java.io.tmpdir from MAVEN_OPTS should be inherited when forking
> ---------------------------------------------------------------
>
>                 Key: SUREFIRE-764
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-764
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin, process forking
>    Affects Versions: 2.9
>         Environment: n/a
>            Reporter: Anders Hammar
>
> For Maven 3 freestyle jobs in Hudson you can select "Private temporary directory". This will set "MAVEN_OPTS=-Djava.io.tmpdir=..." for the Maven execution.
> However, surefire/failsafe plugin forks by default and the forked process will then not be using this temp directory as the new JVM settings are not inherited from MAVEN_OPTS.
> I'm suggesting that java.io.tmpdir should be inherited from MAVEN_OPTS, if specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)