[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23768: ------------------------------------ Yes, ideally we'd release the parent pom BEFORE everything that depends on it goes to Final/GA... but in this case there were a few changes to the parent pom I needed to do AFTER the GA builds were done. https://github.com/jbosstools/jbosstools-build/commits/jbosstools-4.4.3.x... Since none of these affect downstream builds (they're just in support of being able to release the pom to Nexus) I didn't feel the need to rebuild everything using the .Final version after releasing it. So in future we can do this: * branch (4.4.4.x and later again for 4.5.0.x) * update parent pom to use correct "stable branch" settings [1] & update version (remove -SNAPSHOT) [2] * trigger build which will now auto-release it to Nexus [3] [1] https://github.com/jbosstools/jbosstools-build/commit/34d346227e412e354e3... [2] https://github.com/jbosstools/jbosstools-build/commit/25e2ae4e00ccbbd2236... [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)