[
https://jira.codehaus.org/browse/SUREFIRE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360612#comment-360612
]
Tibor Digana edited comment on SUREFIRE-764 at 1/4/15 9:13 AM:
---------------------------------------------------------------
@Anders
I guess this won't be possible in 2.x.
You can use
{code}
<argLine>${env.MAVEN_OPTS}</argLine>
{code}
We don't want to add new configuration parameter right before the EO surefire
2.x.
I guess in surefire 3.0 you should have a chance to hack via SPI, Java 8 extra
module, maybe Bash Shell if JavaScript or so, without asking us to do it.
Do you agree with me to assign this issue to 3.0?
was (Author: tibor17):
@Anders
I guess this won't be possible in 2.x. You can use argLine=${env.MAVEN_OPTS}.
We don't want to add new configuration parameter right before the EO surefire
2.x.
I guess in surefire 3.0 you should have a chance to hack via SPI, Java 8 extra
module, maybe Bash Shell if JavaScript or so, without asking us to do it.
Do you agree with me to assign this issue to 3.0?
> 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)
