You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Daniel Takai (JIRA)" <ji...@codehaus.org> on 2007/02/09 18:06:44 UTC
[jira] Commented: (MASSEMBLY-163) In a multiproject environment
Assembly causes many unneded rebuilds
[ http://jira.codehaus.org/browse/MASSEMBLY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87199 ]
Daniel Takai commented on MASSEMBLY-163:
----------------------------------------
We've encountered the same bug today and second the reported behaviour. This is critical since no workaround is known. We'd have to revise large portions of the build infrastructure or write our own plugin to fix. Please!
> 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
>
> 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