Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.6
-
None
-
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: C:\projects\build\apache-maven-3.3.9\bin\..
Java version: 1.8.0_102, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_102\jre
Default locale: en_US, platform encoding: Cp1250
OS name: "windows server 2008 r2", version: "6.1", arch: "amd64", family: "dos"Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: C:\projects\build\apache-maven-3.3.9\bin\.. Java version: 1.8.0_102, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_102\jre Default locale: en_US, platform encoding: Cp1250 OS name: "windows server 2008 r2", version: "6.1", arch: "amd64", family: "dos"
-
Unknown
Description
When assembly plugin is used together with cxf codegen plugin, it is using up massive amount of memory, leading to frequent OOM errors and long build times. When used alone, both plugins behave nicely.
Attached POM can be used to replicate the issue. When CXF plugin is commented out, assembly plugin finishes within a few seconds, using up minimal amount of memory. When the POM is executed as provided, Maven throws OOM when given 2GB of memory.
See also MASSEMBLY-825 for related assembly-plugin report.