JIFENG ZHANG created SUREFIRE-1035:
--------------------------------------
Summary: Use the same settings as "parental" JVM when forking a JVM
Key: SUREFIRE-1035
URL: https://jira.codehaus.org/browse/SUREFIRE-1035
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin, process forking
Affects Versions: 2.16
Reporter: JIFENG ZHANG
When forking a JVM, JVM settings are not inherited from MAVEN_OPTS. And by
default, the forked JVM is a new instance of the same JVM used to start Maven.
Were there strong reasons for not using the same JVM settings as the "parental"
JVM, but using argLine explicitly?
I think for the users that are not aware of JVM forking, they would expect the
same JVM settings are used when running surefire plugin. Just like we assumed
it is the same JVM (new instance) forked as the one Maven runs on, which was
not true until version 2.3, and was fixed in
[SUREFIRE-135|https://jira.codehaus.org/browse/SUREFIRE-135]
So I propose when forking a JVM, the same settings from JVM that maven runs on,
is used; unless there is an argLine explicitly overwrites the settings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
