-
Notifications
You must be signed in to change notification settings - Fork 26
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
Comments
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 |
Yea, sorry, didn't properly check the Readme. I think this should be added to the parameters or FAQ section, something like this: Otherwise, the task |
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! |
Closing as 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 . |
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?
The text was updated successfully, but these errors were encountered: