maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] (SUREFIRE-764) from MAVEN_OPTS should be inherited when forking
Date Sun, 04 Jan 2015 15:07:14 GMT


Tibor Digana commented on SUREFIRE-764:

I guess this won't be possible in 2.x. You can use argLine, however there's no connection
in argLine syntax to link MAVEN_OPTS with argLine.
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 do this via SPI or so, without asking
us to do it.
Do you agree with me to assign this issue to 3.0?

> from MAVEN_OPTS should be inherited when forking
> ---------------------------------------------------------------
>                 Key: SUREFIRE-764
>                 URL:
>             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 "" 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 should be inherited from MAVEN_OPTS, if specified.

This message was sent by Atlassian JIRA

View raw message