[
http://jira.codehaus.org/browse/CONTINUUM-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Catherine Tan updated CONTINUUM-1815:
-------------------------------------------
Fix Version/s: (was: 1.2.1)
1.4.0
I tried this in the continuum-flat-multi-module branch and using a single
checkout directory for a multi-module project fixes this problem. So i'm
changing the fix version for this to 1.4.0
> 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.4.0
>
> 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
