You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Napoleon Esmundo C. Ramirez (JIRA)" <ji...@codehaus.org> on 2008/09/23 08:55:45 UTC
[jira] Updated: (CONTINUUM-1815) Scheduled build loses track of
proper reactor order after a release
[ http://jira.codehaus.org/browse/CONTINUUM-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Napoleon Esmundo C. Ramirez updated CONTINUUM-1815:
---------------------------------------------------
Attachment: multimodule-project.tar.gz
Attached a tarball of the multimodule project I used for this issue (multimodule-project.tar.gz).
It contains:
{noformat}
multimodule-parent
|
+-- submodule-one
|
+-- submodule-two
|
+-- submodule-three
{noformat}
three depends on one, one depends on two. So the the build order should go parent-->two-->one-->three.
> Scheduled build loses track of proper reactor order after a release
> -------------------------------------------------------------------
>
> Key: CONTINUUM-1815
> URL: http://jira.codehaus.org/browse/CONTINUUM-1815
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
> Affects Versions: 1.1
> Reporter: Napoleon Esmundo C. Ramirez
> Priority: Minor
> Fix For: 1.3
>
> Attachments: multimodule-project.tar.gz
>
>
> After a release, the scheduled build fails because the build order doesn't start with the parent. The parent doesn't get built first because the last build status of the parent is already green--and so builds the submodules first. To work this out, a manual build should be triggered.
--
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