[
https://issues.apache.org/jira/browse/SLING-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377484#comment-14377484
]
Oliver Lietz commented on SLING-4530:
-------------------------------------
That makes sense. I couldn't find documentation for the behavior when
{{.mvn/jvm.config}} is used and running with {{-X}} doesn't give any useful
information either (http://jira.codehaus.org/browse/MNG-5785). But after
running some builds it looks like these settings are _added_ and do not
override the ones from {{MAVEN_OPTS}}.
> Add .mvn/jvm.config to reactor
> ------------------------------
>
> Key: SLING-4530
> URL: https://issues.apache.org/jira/browse/SLING-4530
> Project: Sling
> Issue Type: Bug
> Components: General
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
>
> Maven 3.3.1 has added the possibility of storing the JVM configuration in a
> .mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm
> options and command line parameters|http://jira.codehaus.org/browse/MNG-5767]
> ). Those flags will apply to all builds by default.
> We should add the flags specified in SLING-443 and SLING-1782 to make sure
> that we have everyone building Sling with the required flags OOTB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
