This repository was archived by the owner on May 25, 2023. It is now read-only.
Added publish commands to build. Now publishes to Sonatype. #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| An update - Sync to Maven Central has happened. We now have |
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
This PR adds the capability to publish artifacts to Sonatype.
Publish to Sonatype is quite unstable as the staging process (
publishSigned) frequently fails with gateway timeout exception (http code: 504). Was able to dopublishSignedafter a few attempts. Then when I tried to close the staging repo (as per the workflow), the Sonatype UI threw a 500 exception. But I found that all the artifacts have been copied toreleasesfolder. Though sync to Maven Central has not yet happened.I raised the issue in #tooling Slack channel and awaiting any suggestion.
Any better alternative welcome!