We could move the tag(s) too, if you need. That's easy enough and
while it doesn't 100% depict reality to say that the build used the
4.4.3.Final parent pom, rather than the 4.4.3.Final-SNAPSHOT one, it
does make reproducibility easier.
But since it's HIGHLY unlikely we'll be rebuilding 4.4.3.x when we
have a 4.4.4.AM1 release coming up in a mere 13 days, I wouldn't worry
too much about it.
Do please document process snafus in JIRA so that we can achieve a
better workflow for future releases.
On Wed, Mar 1, 2017 at 8:14 AM, Martin Malina <mmalina(a)redhat.com> wrote:
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
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.
> On 24 Feb 2017, at 22:51, Nick Boldt <nboldt(a)redhat.com> 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 .
> I also released 4.3.2.Final  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
> For more on this, see: https://issues.jboss.org/browse/JBIDE-23768
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> jbosstools-dev mailing list
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio