Fix Maven Central publishing - #29
Merged
Merged
Conversation
- Add --fail flag to curl to fail build on HTTP errors - Add verbose logging (-v) for better debugging - Add bundle structure verification step - Improve bundle creation with file listing
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Maven Central publishing job failed with HTTP 500 error, but the build was marked as successful because curl returns exit code 0 even on HTTP errors.
Solution
Error Handling
Bundle Verification
Improved Bundle Creation
Changes
Testing
After merging, this will help identify the root cause of the HTTP 500 error from Sonatype.