[
http://jira.codehaus.org/browse/MASSEMBLY-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210913#action_210913
]
Arnaud Heritier commented on MASSEMBLY-424:
-------------------------------------------
Same problem here : http://svn.exoplatform.org/projects/jcr-benchmark/trunk/
This is a regression in the plugin.
Here are some tests (mvn clean install) with this "little" project with an
assembly using a dependencySet (tested at least 3 times per version to validate
the time) :
with assembly plugin 2.1 : 10s
with assembly plugin 2.2-beta-1 : 11s
with assembly plugin 2.2-beta-2 : 22s
with assembly plugin 2.2-beta-3 : 36s
with assembly plugin 2.2-beta-4 : 36s
with assembly plugin 2.2-beta-5 : 36s
I change the priority to critical because the plugin is quite useless if we use
this feature on a real project. I have a case where the plugin takes several
minutes to build the assembly.
On some environments where IOs are worst than on mine laptop, the ratio is more
important.
> poor performance of dependencySet in assembly descriptor (compared to using
> maven-dependency-plugin + fileSet)
> --------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-424
> URL: http://jira.codehaus.org/browse/MASSEMBLY-424
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-4
> Environment: maven 2.1.0, java 6u13, os x 10.5.6, macbook pro 5400rpm
> disk
> Reporter: Cameron Fieber
> Priority: Minor
>
> The performance of the dependencySet element in the assembly descriptor is
> significantly worse than achieving the equivalent result by doing an
> execution of dependency:copy-dependencies and including the
> target/dependencies folder as a fileSet in the assembly descriptor
> replacing:
> <assembly>
> ...
> <dependencySets>
> <dependencySet>
> <outputDirectory>lib</outputDirectory>
> </dependencySet>
> </dependencySets>
> ...
> </assembly>
> with:
> <assembly>
> ...
> <fileSet>
> <directory>${project.build.directory}/dependency</directory>
> <outputDirectory>lib</outputDirectory>
> </fileSet>
> ...
> </assembly>
> and (in pom.xml):
> ...
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal>copy-dependencies</goal>
> </goals>
> <configuration>
> <includeScope>runtime</includeScope>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
