Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
In all our java projects, we have a fairly basic assembly configuration, something like this:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.6</version>
<configuration>
<archive>
<manifest>
<mainClass>org.x.x.x</mainClass>
</manifest>
</archive>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
They all take about 10x longer with any 3.x.x version of the maven assembly plugin than the 2.6 version.
This has been noticed by others:
But not reported as a bug that I could find.
Although I could only justify "Minor" for the priority, this is really is a blocker for us moving to 3.x.x
The upgrade is just not worth taking your build from < 10 sec to > 50 sec.
(For this particular build, it went from about ~ 7 sec to ~ 57 sec.)
Attachments
Attachments
Issue Links
- blocks
-
MPOM-196 Update maven-assembly-plugin to 3.1.1
- Closed
- depends upon
-
MASSEMBLY-900 Upgrade plexus-archiver to 4.0.0
- Closed
- is duplicated by
-
MASSEMBLY-873 Maven-Assembly-Plugin freezes when building jar-with-dependencies of project depending on org.bouncycastle:bcprov-jdk15on:1.58
- Closed
- relates to
-
MASSEMBLY-888 jar-with-dependencies performance can be greatly improved by using the cache
- Closed