maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anders Hammar (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-764) java.io.tmpdir from MAVEN_OPTS should be inherited when forking
Date Sun, 04 Jan 2015 15:17:10 GMT

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

Anders Hammar commented on SUREFIRE-764:
----------------------------------------

Sure, that's ok.

> java.io.tmpdir from MAVEN_OPTS should be inherited when forking
> ---------------------------------------------------------------
>
>                 Key: SUREFIRE-764
>                 URL: https://jira.codehaus.org/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.1.6#6162)

Mime
View raw message