You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2012/11/20 07:55:13 UTC
[jira] (CONTINUUM-1606) All modules are always rebuilt when using
M2 with a hierarchical structure
[ https://jira.codehaus.org/browse/CONTINUUM-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1606:
------------------------------------
Fix Version/s: (was: Backlog)
1.5.0
> All modules are always rebuilt when using M2 with a hierarchical structure
> --------------------------------------------------------------------------
>
> Key: CONTINUUM-1606
> URL: https://jira.codehaus.org/browse/CONTINUUM-1606
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.1
> Reporter: Julien S
> Priority: Critical
> Fix For: 1.5.0
>
> Attachments: continuum-1.2.patch, CONTINUUM-1606.patch, continuum.patch
>
>
> When using Maven2, the recommended directory structure for a multi-module build is hierarchical, e.g.:
> - pom.xml (parent pom of all modules)
> --- module1
> +-- pom.xml
> --- module2
> +-- pom.xml
> etc
> When using such a structure with continuum, if a change is committed in module28, then EVERY module will be rebuilt: indeed the parent pom will be rebuilt because the change is "under" its scm tree, and all the other modules will therefore we rebuilt because of a "dependencies change" on the parent pom. This can easily multiply the build time by a factor of 10 or 20.
> I have attached a patch. It considers that the parent has "changed" only if its pom.xml has changed. Not sure it is perfect, but it works for me (the patch has been tested (against continuum-1.1 and trunk). Feel free to rewrite or modify it as much as you like.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira