Move to gradle-nexus.publish-plugin #1495
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Publishing to Maven is sometimes flaky, producing the warning
This is a known issue with https://github.com/Codearte/gradle-nexus-staging-plugin , and the creator recommends using https://github.com/gradle-nexus/publish-plugin instead. This PR follows the migration steps in https://github.com/gradle-nexus/publish-plugin/wiki/Migration-from-gradle_nexus_staging-plugin---nexus_publish-plugin-duo.
Testing
Verified that publish action works when the command is
./gradlew publishToSonatype closeSonatypeStagingRepository
. It finishes successfully and I manually inspected that the artifacts look good in Nexus UI, then dropped the staged repositories.The command is now
./gradlew publishToSonatype closeAndReleaseSonatypeStagingRepository
, but I'm not sure how to test that part without actually releasing.