You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Zoran Regvart (JIRA)" <ji...@apache.org> on 2019/05/09 18:18:01 UTC
[jira] [Resolved] (CAMEL-13496) maven-invoker-plugin taking as much
heapspace as the Maven itself
[ https://issues.apache.org/jira/browse/CAMEL-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoran Regvart resolved CAMEL-13496.
-----------------------------------
Resolution: Fixed
> maven-invoker-plugin taking as much heapspace as the Maven itself
> -----------------------------------------------------------------
>
> Key: CAMEL-13496
> URL: https://issues.apache.org/jira/browse/CAMEL-13496
> Project: Camel
> Issue Type: Bug
> Components: build system
> Reporter: Zoran Regvart
> Assignee: Zoran Regvart
> Priority: Major
> Fix For: 2.24.0, 3.0.0-M3, 2.23.3
>
>
> When we run {{maven-invoker-plugin}} it takes on any {{MAVEN_OPTS}} or {{.mvn/jvm.config}} settings and runs with those. We specify 3.5GB of heap for the Maven process in {{.mvn/jvm.config}} so for each invocation {{maven-invoker-plugin}} will start a JVM with additional 3.5GB of heap.
> There is no way of overriding the entire JVM configuration, but luckily the last {{-Xmx}} setting on the JVM command line is taken into consideration, so when configuring the {{maven-invoker-plugin}} we can set the {{<mavenOpts>}} configuration and it will be appended to the {{java}} command line arguments and the last {{-Xmx}} parameter will set the heap size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)