Re: [ee4j-build] Wrong release in staging

[Christian Kaltepoth <christian@xxxxxxxxxxxx>]

I think it is even worse. This artifact has already hit Maven Central:

https://search.maven.org/search?q=g:jakarta.persistence

Am Fr., 2. Nov. 2018 um 12:18 Uhr schrieb Maxim Nesen <maxim.nesen@xxxxxxxxxx>:

Hello,

Today I've released a version of JPA using job
https://jenkins.eclipse.org/jpa/job/jpa-api-release-finalize
to
https://oss.sonatype.org/content/groups/staging/jakarta/persistence/jakarta.persistence-api/2.2.1/

However later on it appeared that this release is not complete and I
would like to drop it and re-release the same (but corrected) version again.

Is it possible to do so?

Thanks and regards,

Maxim

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build

--

Christian Kaltepoth

Blog: http://blog.kaltepoth.de/

Twitter: http://twitter.com/chkal

GitHub: https://github.com/chkal