I added a test in ProjectSorterTest in r.772047, the issue isn't with the ProjectSorter

This happens because continuum is disregarding the dependency orders of projects that are not part of a multi-module hierarchy because of the changes made for the group update.

In addition to fixing the order of builds of a non multi-module in a group,

[1] projects within the same group will build in the same "build queue/build agent"

or

[2] projects will build in the same "build queue/build agent" of it's "SNAPSHOT" dependency

[1] is easier to implement and less expensive
[2] can optimize the use of build queues and build agent

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

I think [1] is fine... most of the time, a project group contains a single multi-module project hierarchy anyway, and it's vitally important that things get built in the right order within a group.

If you were going to do [2], it should notice that the ear depends on both wars and build them all in one queue. That the wars can be build independently is not relevant since they must both be built before the ear. Not everyone uses SNAPSHOT version numbers so that shouldn't be a consideration. Maybe we can leave this optimization open for a future enhancement.

Fixed in

r775693, r775726 of 1.3.x branch
r775729 of trunk