Sonatype migrating from OSSHR to a new Maven Central

ringods commented 2 months ago

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

This issue is to create awareness around the effort Sonatype is doing to migrate the main Java package repository to a new backend.

OSSHR (Legacy) - generated pom.xml files uses this way of publishing
Central Portal (New) - support should be added to publish via this new API

There is no timeline yet when the legacy repository will be phased out.

Affected area/feature

Publishing of Java SDKs.

ringods commented 2 months ago

Is it possible to add support for the new way as an addition to the generated pom.xml files? With Pulumiverse, we already opted to the new Central Portal. Without the support in the pom.xml files, we can't publish Java SDKs.

t0yv0 commented 1 week ago

Do you have a fully working example, this would be appreciated. I am currently looking into the internal publishing of Pulumi Java providers which stopped working, it utilizes Gradle however.

pulumi / pulumi-java