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

How to handle DEPRECATION WARNING. The staging repository ID is not provided? #127

Open
pwittchen opened this issue Aug 6, 2019 · 4 comments

Comments

@pwittchen
Copy link

commented Aug 6, 2019

Hi,

I used Gradle task closeAndReleaseRepository and got the warning:

DEPRECATION WARNING. The staging repository ID is not provided. The fallback mode may impact release reliability and is deprecated. Please consult the project FAQ how it can be fixed.

What should I do? Where should I provide repository ID and what does it really mean?

@szpak

This comment has been minimized.

Copy link
Member

commented Aug 7, 2019

See the point in FAQ to add nexus-publish-plugin to better handle a staging repository resolution.

I will keep the issue open as I plan to rework the FAQ, the error message or even apply the nexus-publish-plugin automatically in a default configuration to make it more natural in reception.

@szpak szpak added the question label Aug 7, 2019

@pwittchen

This comment has been minimized.

Copy link
Author

commented Aug 7, 2019

Do I really need nexus-publish-plugin? I publish artifacts with custom groovy/gradle script and it works well and use gradle-nexus-staging-plugin for closing and releasing the artifacts. I don't want to add another dependency to the project (which I'm not going to use) just to remove the warning. I don't see any benefits from this as I already have working solution :). Maybe I'll wait for updated FAQ.

@szpak

This comment has been minimized.

Copy link
Member

commented Aug 7, 2019

If you are not using Travis (or anything else that sends subsequent requests via different IP addresses) and release on project at the time (+ you manually clean up old staging repositories if anything goes wrong) then GNSP should enough for you (the feature is deprecated and I don't have any intermediate plans to remove it).
However, as described in the FAQ, in this issue and in my blog post much more reliable is using GNPS together with NPP.

Btw, I rather planned to update FAQ how to start using NPP, not how to suppress the warning :).

@pwittchen

This comment has been minimized.

Copy link
Author

commented Aug 7, 2019

Ok, I'll check it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.