Repository navigation
Send publishingType to Maven Central as a query parameter - #476
Merged
Merged
Conversation
The Central Portal's upload API takes publishingType as a query parameter and defaults to USER_MANAGED, so sent as a form field it can be ignored, leaving the deployment to be published by hand.
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.
The Maven Central job uploads the bundle with
publishingType=AUTOMATICas a multipart form field. The Central Portal API documentspublishingTypeas a query parameter that defaults toUSER_MANAGED. Sent as a form field, it can be ignored: the deployment then validates but waits for someone to publish it by hand in the Portal.This sends it as a query parameter instead, and doesn't change anything else.