cool, release:perform succeeded, now the artifacts are on a single Nexus
staging repo.
I'm pushing the artifacts to /dist and will open the VOTE once uploading
has finished (hopefully before I get old).

Regards,
Tommaso

Il giorno gio 23 feb 2017 alle ore 15:39 Matt Post <p...@cs.jhu.edu> ha
scritto:

> Thank you for heading this up, Tommaso! I'll be able to catch up on this
> after today.
>
> matt
>
>
> > On Feb 23, 2017, at 3:06 AM, Tommaso Teofili <tommaso.teof...@gmail.com>
> wrote:
> >
> > probably because of the mentioned network issues the artifacts ended up
> in
> > two separate staging repositories in Nexus, which is undesired.
> > I'll drop those repos, rollback the changes on the pom, delete the
> current
> > tag in git and perform again mvn release:prepare / perform today.
> >
> > Regards,
> > Tommaso
> >
> > Il giorno mer 22 feb 2017 alle ore 16:39 Tommaso Teofili <
> > tommaso.teof...@gmail.com> ha scritto:
> >
> >> Hi all,
> >>
> >> Maven is in the extremely slow (because of my bandwidth) process of
> >> deploying stuff on Nexus as part of the mvn release:perform phase.
> >> In the meantime perhaps is a good idea not to commit to the master
> branch,
> >> until we get the RC3 voted and hence approved / rejected.
> >>
> >> Thanks and regards,
> >> Tommaso
> >>
>
>

Reply via email to