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 2008/04/02 12:53:58 UTC
[jira] Updated: (CONTINUUM-1312) Build trigger issue in multimodule
project
[ http://jira.codehaus.org/browse/CONTINUUM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1312:
------------------------------------
Fix Version/s: (was: Future)
1.x
> Build trigger issue in multimodule project
> ------------------------------------------
>
> Key: CONTINUUM-1312
> URL: http://jira.codehaus.org/browse/CONTINUUM-1312
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.1-alpha-2
> Reporter: Julien S
> Fix For: 1.x
>
>
> If you have a multimodule project with the parent pom at the top level directory, e.g.:
> + pom.xml
> +- module1
> +- pom.xml
> +- module2
> +- pom.xml
> Etc
> Then, a modification to any module will trigger the build of ALL modules.
> This is obviously because a change in a module will be detected at the top level, and that if the top level is modified, all its subprojects are rebuilt.
> A solution may be to put the parent POM at the same level as the others, but this triggers other problems...
> It would be nice to a solution at the continuum level.
--
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