Migrate to Sonatype Central Portal

[gastaldi]

This migrates from OSSRH (s01.oss.sonatype.org) to Central Portal

• Fixes Migrate to mavenCentral deployer #12

[gastaldi]

@aalmiray the deployment failed with 401 Unauthorized(), what am I missing? https://github.com/quarkiverse/quarkiverse-release/actions/runs/14115879010

Here is the jreleaser.yml: https://github.com/quarkiverse/quarkiverse-release/blob/main/jreleaser.yml

[aalmiray]

Did you register a new username/token for the Portal API? Is the quarkiverse namespace associated with the new username?

[aalmiray]

FWIW snapshot support for the mavenCentral deployer does not work at all at the moment. Long story short it turns out a different API is required to publish snapshot releases.

[gastaldi]

Ah, I forgot that step, perhaps it is worth mentioning it in the https://jreleaser.org/guide/latest/reference/deploy/maven/maven-central.html docs. Thanks!

[gastaldi]

FWIW snapshot support for the mavenCentral deployer does not work at all at the moment. Long story short it turns out a different API is required to publish snapshot releases.

Hm, that's a problem because once you migrate to the Portal, you can't go back to OSSRH. Any timeframe when a fix is provided?

[aalmiray]

It’s possible to publish snapshots but the solution is weird at the moment. For some reason, Sonatype decided to support snapshot deployments using a nexus2 instance whose endpoint is described at https://central.sonatype.org/publish/publish-portal-snapshots/#publishing-via-other-methods

Technically you’d configure a mavenCentral deployer for stable releases and a nexus2 deployer for snapshot releases. I know, this is confusing, and thus we’ll find a way to configure just one deployer, mavenCentral, and route the calls to the corresponding deployer under the covers.