[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15606: ------------------------------------ In the past this step's not been needed, because the whole stack just rebuilt itself even if nothing had changed. But going forward, we're trying to be better about "nothing changed == no respins", so I need to have 1 repo per component that won't be changing in the next release. The reason I don't want to put in specific versions is that it means maintaining that information in multiple places: 1. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... composite*.xml 2. https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.... 3. https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.... etc. What I'd like to do is find the midground between "release every component by itself AS WELL as JBT aggregate" (too much work - especially if some projects start out unchanged for Alpha1 and then later end up changing for Alpha2, like Forge; or like Freemarker which didn't change at all during the JBT 4.1.0 cycle until after Beta, IIRC) and "oops, we need to go back and re-aggregate a few projects". -- 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