-
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
closeRepository
task run before publishing all subprojects
#157
Comments
The usage with In the meantime, you may want to add it manually in your project. |
@szpak You are absolutely right 👍 And, of course, the next configuration helped me.
But I thought, that this configuration of tasks ordering already implemented in the plugin 😄 |
@vlsi You have |
If it failed due to timeout, then in 99.84% of the cases it means the operation is in progress at the Nexus side. No retry is required in that case. In extreme cases, there always is an option to open Nexus UI and release the repository. Note: |
Sure, that's why I mentioned
If you have just one, it's not a problem. With the new plugin there is an option to specify the ID. |
TL;TD. This case is already improved in gradle-nexus-publish-plugin. A longer version. To make releasing to Maven Central even easier, I and Marc Phillip (the author of nexus-publish-plugin) combined forces to create a next generation, unified, 2-in-1 plugin - gradle-nexus-publish-plugin. It is a recommended solution, as our development effort will be put in that new plugin. See my blog post and the official migration guide. |
Thank you @szpak! One repo we already migrated to GNPP 👍 |
Given
id("de.marcphilipp.nexus-publish") version "0.4.0"
Reproducing
nexus_plugins
-SNAPSHOT
from version in/build.gradle.kts
packageGroup
for your../gradlew clean publishToSonatype closeRepository -x test
Dry Run
Dry run log is correct and
closeRepository
task is latest.The text was updated successfully, but these errors were encountered: