continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "apache maillist (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1606) All modules are always rebuilt when using M2 with a hierarchical structure
Date Tue, 14 Oct 2008 22:07:51 GMT


apache maillist commented on CONTINUUM-1606:

it would be very nice if you could test the case below:
-- pom.xml - for continuum checking out 3 modules below
   -- parent module (parent pom for module1 and module2)
   -- module 1
   -- module 2

> All modules are always rebuilt when using M2 with a hierarchical structure
> --------------------------------------------------------------------------
>                 Key: CONTINUUM-1606
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Integration - Maven 2
>    Affects Versions: 1.1
>            Reporter: Julien S
>            Priority: Critical
>             Fix For: 1.x
>         Attachments: continuum-1.2.patch, CONTINUUM-1606.patch, continuum.patch
> When using Maven2, the recommended directory structure for a multi-module build is hierarchical,
> - 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 contact one of the administrators:
For more information on JIRA, see:


View raw message