Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 65F3B17ED0 for ; Sat, 10 Oct 2015 23:19:10 +0000 (UTC) Received: (qmail 39815 invoked by uid 500); 10 Oct 2015 23:19:05 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 39760 invoked by uid 500); 10 Oct 2015 23:19:05 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 39744 invoked by uid 99); 10 Oct 2015 23:19:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Oct 2015 23:19:05 +0000 Date: Sat, 10 Oct 2015 23:19:05 +0000 (UTC) From: "Tibor Digana (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (SUREFIRE-1035) Use the same settings as the maven JVM when forking a JVM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SUREFIRE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1035: -------------------------------------- Assignee: Tibor Digana > Use the same settings as the maven JVM when forking a JVM > --------------------------------------------------------- > > Key: SUREFIRE-1035 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1035 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin, process forking > Affects Versions: 2.16 > Reporter: Jifeng Zhang > Assignee: Tibor Digana > > 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 was sent by Atlassian JIRA (v6.3.4#6332)