[
http://jira.codehaus.org/browse/MASSEMBLY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-163.
--------------------------------
Assignee: John Casey
Resolution: Fixed
Fix Version/s: 2.2-beta-2
I'd suggest using the assembly:single goal (if you don't already). Also, since
2.2-beta-1, dependencies are only resolved on-demand, if they are needed for
that particular type of assembly.
> In a multiproject environment Assembly causes many unneded rebuilds
> --------------------------------------------------------------------
>
> Key: MASSEMBLY-163
> URL: http://jira.codehaus.org/browse/MASSEMBLY-163
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: Linux Gentoo, Java 1.5.0_07_b3 sun, Maven 2.0.4, plugin
> 2.1
> Reporter: Simone Gianni
> Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I have a project subdivided in 10 modules. 2 of these modules uses the
> assembly plugin with the built-in descriptor "jar-with-dependencies".
> When running mvn clean install (or also only maven install) from the root of
> the project, I see that every time it is building one of the two sub-projects
> that uses the assembly plugin, it rebuilds some already built projects, even
> if they are not dependencies of the "to be assembled" project, nor they have
> any other apparent motivation to be rebuilded. One of the two project using
> assembly doesn't even has a single dependency on other project, but triggers
> a nearly complete rebuild.
> One of the projects is a WAR overlaying another war, useless to say that it
> consumes a lot of time, and gets built 3 times.
> I've tested also with -o to exclude possible changes in external
> dependencies, checked all the dependency tree to make sure that there were no
> circular or otherwise "crossed" dependencies, changed the order of <modules>
> in the parent pom to the best build order, checked by hand starting from an
> empty local repository that building the artifacts (by hand, one by one,
> commenting out the assembly) in that order satisfies all the dependencies.
--
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
