You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@continuum.apache.org by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org> on 2009/05/23 00:37:42 UTC

[jira] Reopened: (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 ]

Maria Catherine Tan reopened CONTINUUM-1815:
--------------------------------------------


We need to revert changes made to this

> 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
>            Assignee: Maria Catherine Tan
>            Priority: Minor
>             Fix For: 1.2.1
>
>         Attachments: continuum.log, 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