I tried to run a test on the jbosstools-4.4.3.Final tag of jbosstools-server and it fails, because the pom still points to 4.4.3.Final-SNAPSHOT parent pom. This is understandable. But could we perhaps do the parent pom release before the tagging and have the released version in the tag next time, please? Right now my only option is probably make this change in 4.4.3.x and use that. -Martin > On 24 Feb 2017, at 22:51, Nick Boldt <nboldt(a)redhat.com&gt; wrote: > > Recently, the Integration Stack guys requested that we start releasing > parent poms. > > So, today, the 4.4.3.Final parent pom has been released [1]. > > [1] https://repository.jboss.org/nexus/#nexus-search;gav~org.jboss.tools~pare... > > I also released 4.3.2.Final [1] parent pom as I was testing some > automation / scripting of nexus staging and release steps. I can now > do a release to Nexus completely from a Jenkins job, without having to > do any manual steps. \0/ > > If you depend on either the 4.3.2.Final-SNAPSHOT or the > 4.4.3.Final-SNAPSHOT parent poms, please update your root poms > accordingly (to remove "-SNAPSHOT") as Nexus will purge the snapshots > soon. > > For more on this, see: https://issues.jboss.org/browse/JBIDE-23768 > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev