-
Notifications
You must be signed in to change notification settings - Fork 30
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
Support Nexus Pro 3 #320
Comments
Nexus 3 is rewritten a piece of software from scratch with completely different API. This plugin supports only Nexus 2 which powers The Central Repository (aka Maven Central). I also haven't heard about the Sonatype plans to switch publishing to TCR to Nexus 3. The main use case it to publish artifacts to TCR.
It looks like the completely new API. I would be probably hard to maintain both APIs (and related workflows) in the same plugin. Let's keep this request open, but probably it would be easier to write a separate plugin for that (but I haven't analized the problem in depth). |
Thanks for the clarification. I wasn't aware, that Nexus 3 is a completely rewritten Software. I totally agree, that it doesn't make sense to squeeze support for both Nexus versions into this plugin. In case, the Sonatype Enterprise Support shares some best practices with me, how to publish to Nexus Pro 3 from Gradle, I am going to share it here. |
Good idea. I believe, you are the second person with the similar problem. Would you like to create a PR with the proposed change?
👍 |
Hi,
io.github.gradle-nexus.publish-plugin
fails with http 404, when I try to use it with Nexus Pro 3:The REST API of Nexus Pro 3 (3.63.0-01) doesn't seem to offer any endpoint for
stagingProfiles
. Instead, one is supposed to tag artifacts and stage them by moving them to another repository (/v1/staging/move/{destination}?tag=...
).Do I assume correctly, that this Plugin is only compatible with Nexus Pro 2.x?
If this plugin could offer to add a tag to each published artifact, this would help a lot for staging or dropping a set of artifacts.
The text was updated successfully, but these errors were encountered: