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

Nexus staging plugin connects to old OSS server. The new one should be https://s01.oss.sonatype.org #200

Closed
therock24 opened this issue Apr 13, 2021 · 5 comments

Comments

@therock24
Copy link
Contributor

This plugin is not working for newer modules that are being published, because sonatype is assigning them to the https://s01.oss.sonatype.org staging server, which is the new server.

The plugin still tries to connect to https://oss.sonatype.org, which will not work as the module is not registered on that server.

Can this be changed by any chance to allow setting a different staging repository URL?

@szpak
Copy link
Member

szpak commented Apr 13, 2021

A default server for the plugin is https://oss.sonatype.org , which is sane as the majority of projects leave there. The new projects use a different server and you - as described in readme - can configure the serverUrl variable to match your needs. Please let me know, if it is not enough.

@therock24
Copy link
Contributor Author

A default server for the plugin is https://oss.sonatype.org , which is sane as the majority of projects leave there. The new projects use a different server and you - as described in readme - can configure the serverUrl variable to match your needs. Please let me know, if it is not enough.

Yea, sorry, didn't properly check the Readme.
Setting the serverUrl to the new server fixed the issue.

I think this should be added to the parameters or FAQ section, something like this:
Important. Users registered in Sonatype after 24 February 2021 need to customize the serverURL:
serverUrl = https://s01.oss.sonatype.org/service/local/

Otherwise, the task closeAndReleaseRepository will fail with 403: Forbidden, attempting to connect to the old server.

@szpak
Copy link
Member

szpak commented Apr 13, 2021

Definitely it is a good idea. Would you like to provide a PR with those changes? :-)

@therock24
Copy link
Contributor Author

Definitely it is a good idea. Would you like to provide a PR with those changes? :-)

Yea, I was just thinking about it, I will do it. Thanks for the quick reply!

@szpak
Copy link
Member

szpak commented Apr 14, 2021

Closing as serverUrl did a trick and your PR has been merged.

Btw, as you setup a new project, you might want to consider a swtich to a new plugin, which is a spiritual continuation of that one. See #193 .

@szpak szpak closed this as completed Apr 14, 2021
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