[ https://issues.jboss.org/browse/JBIDE-12514?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12514: ------------------------------------ +1 for components, especially under the new github reorg strategy (JBIDE-12475). But what about for aggregate builds? should they wait until all their upstream are done? Or spin with the possibility that there's a dependency chain breakage somewhere, eg., that the latest AS depends on a different version of WTP than Openshift, and therefore p2 won't let the two be installed concurrently. By waiting until all the components are done churning, we ensure that everyone's built with each other, and so the aggregate should be more cohesive than if we just grab "whatever's available at that time." But that could also mean it takes DAYS for a clean spin of the aggregates, if all the upstream are constantly churning. Maybe the midground solution here is to always build the aggregates from integration builds instead of nightly? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira