Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are there plans to support publishing through the "Publisher Portal"? #330

Open
NotMyFault opened this issue Apr 6, 2024 · 5 comments
Open

Comments

@NotMyFault
Copy link

Hey,

sonatype shut down registering new namespaces for the OSSRH earlier this year. New registrations are now done through the publisher portal.
If I read the documentation right, there is only a maven plugin at the moment.

It would be awesome if this gradle plugin would support it too, for upcoming namespaces people register.

@szpak
Copy link
Contributor

szpak commented Apr 6, 2024

Briefly reading the documentation, I'm not sure if/when Sonatype plans to retire releasing (new) projects via OSSRH. In addition, I wasn't able to find any developer (API) documentation for releasing (and even their Maven plugin doesn't seem to be available on GitHub, or anywhere else with the source code - or maybe, I just wasn't able to find it *).

@NotMyFault Could you ask the Sonatype guys about that?

Update. There is a link at https://central.sonatype.com/artifact/org.sonatype.central/central-publishing-maven-plugin pointing to https://github.com/sonatype/central-publishing-maven-plugin , but it doesn't seem to be publicly available (yet). Nevertheless, even reverse engineering existing code could be time consuming - the API documentation would be much better (+ their intentions about retiring the old process).

@NotMyFault
Copy link
Author

I'm not sure if/when Sonatype plans to retire releasing (new) projects via OSSRH

Afaik, existing projects can continue to use the "old" workflow to publishing to maven central through OSSRH (for now), but new registrations have to use https://central.sonatype.com/publishing.
Large parts of the pre-existing workflow are already gone, e.g. the Jira instance to request and update release permissions now points to the central portal: https://issues.sonatype.org/

I wasn't able to find any developer (API) documentation

There appears to be a bit at https://central.sonatype.org/publish/publish-portal-api/

Nevertheless, even reverse engineering existing code could be time consuming - the API documentation would be much better

Agreed, I'll happily ask if the source code lives somewhere else. Although there appear to exist a few gradle plugins for the central portal already: https://central.sonatype.org/publish/publish-portal-gradle/
But none of them suffice for my workflow, like yours :(

@szpak
Copy link
Contributor

szpak commented Apr 6, 2024

Thanks for the extra information.

We would probably need to analyze how similar the workflow is and much would it be simple to put it into this plugin to handle it in the other way round. Also, it seems to be still "Publisher Early Access", so the things might change (although the new projects/namespaces seem to need to use the new approach, unless manually migrated to OSSRH :-/ ).

@NotMyFault
Copy link
Author

Also, it seems to be still "Publisher Early Access", so the things might change (although the new projects/namespaces seem to need to use the new approach, unless manually migrated to OSSRH :-/ ).

Yeah, the time to retire the old service was really short. According to the setup docs, all new namespace registrations only happen through the new portal.

@NotMyFault
Copy link
Author

NotMyFault commented Apr 19, 2024

Also, it seems to be still "Publisher Early Access", so the things might change (although the new projects/namespaces seem to need to use the new approach, unless manually migrated to OSSRH :-/ ).

Yeah, the time to retire the old service was really short. According to the setup docs, all new namespace registrations only happen through the new portal.

After reaching out, they told me there are plans to open source the plugin, but no date when this will happen. I could take a look at the -sources jar, if I want to :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants