[ 
http://jira.codehaus.org/browse/CONTINUUM-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175209#action_175209
 ] 

Maria Catherine Tan commented on CONTINUUM-2218:
------------------------------------------------

The problem with [2] is with Wendy's scenario:

WAR1 and WAR2 can be build in 2 different build queue because they have no 
dependencies in each other. How will continuum know where EAR should be queued?

So I guess i'll go with [1].

> Unrelated but inter-dependent projects in the same group are not built in the 
> correct order
> -------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2218
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2218
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.3.2
>            Reporter: Wendy Smoak
>            Assignee: Maria Catherine Tan
>            Priority: Critical
>             Fix For: 1.3.3
>
>
> To reproduce, add three unrelated projects to a project group where one 
> project depends on the other two, such as an EAR that depends on two WARs.  
> They can use a master pom as <parent> but should not be part of a 
> parent-with-modules hierarchy.  
> The expected behavior is for Continuum to build the WARs first and then the 
> EAR, however this is not what happens in my example.  The EAR is built first, 
> causing it to have the wrong/old WARs inside and wasting time spent testing 
> the wrong artifacts.
> This happens whether or not multiple parallel build queues are used.  With 
> multiple queues, Continuum scatters the projects among queues and the build 
> order depends on what finishes first.  When restricted to a single queue, you 
> can see the incorrect order as it moves through the queue.
> Continuum should consider dependencies when ordering projects within a group, 
> even if the projects are not part of a multi-module hierarchy.
> [Unconfirmed regression in 1.3.x.  I believe this worked correctly in 1.2.x  
> as we're getting new problem reports after upgrading, but haven't had time to 
> verify.]

-- 
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

        

Reply via email to