Why don't we deploy RC releases to central?

[James Roper]

Hi all,

I've searched back through the mailing list archives to find an answer to this but couldn't - why don't we deploy RC releases to Maven central?

There's a few problems with just deploying to the Maven central staging repository, and not releasing it, the biggest one is that staging repositories are periodically dropped if they aren't released, which means builds that once used to build, suddenly fail. Even if you fix the build to depend on a new release, I'm not comfortable with that at all, I think it's important to be able to go back to any point in a repositories history, and have a working build, regardless of whether at that point in time, the build depended on final or RC releases, it's one of the big reasons for doing pull request validation.

Not deploying RCs to Maven central is not a practice I've ever come across before in open source, all the open source projects I've been a part of and most of the ones that I've consumed publish all their builds to Maven central, it's not like Sonatype is charging per release. The reason for releasing RCs is to allow the community to test them, but if they aren't deployed to a place that's convenient to consume, how can the community do that?

It also prevents transitive release candidates, lets say an implementation of spec A wanted to deploy its own RC1 of itself that depends on RC1 of the spec. To do that currently, it needs to add that releases staging repository to its pom, but that will cause it to fail Sonatypes pom validation, because you're not allowed custom repository sections in any artifacts deployed to Maven central, Maven central artifacts are all required to be resolvable without any custom repositories.

The solution I've had to use so far is to deploy my own builds of all the artifacts to my own bintray repository, and not use Maven central at all.

Regards,

James

--

James Roper
Architect, Office of the CTO, Lightbend, Inc.
@jroper

[Emily Jiang]

I don't think anyone asked for it in the past. I think it is reasonable for the RCx to be published to maven central.

Emily

[Ondro Mihályi]

I agree, it also makes sense to me to release RC and even MR to maven central.

We probably didn't do it just because we didn't want to make irreversible mistakes in the early MP stage. Now that our release process is stable, it's safe to release all to central

Ondro

[James Roper]

Great thanks! I'll update this page:

https://wiki.eclipse.org/MicroProfile/SpecRelease/Release

To instruct the release to central to be done in both cases.

--
You received this message because you are subscribed to the Google Groups "Eclipse MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/3b006753-b483-4ae8-9816-47dc28ae907d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.