Repository navigation
build(release): update the Central publishing plugin so the bundle validates - #36
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 v0.3.0 release failed twice at Central validation: "Bundle has content that does NOT have a .pom file: com/fopost/fopost-java". The 0.2.0 run logged "Pre Bundling - deleted .../maven-metadata-central-staging.xml"; today's runner no longer gets that cleanup from plugin 0.7.0, so the metadata file ships in the bundle and Central rejects it. 0.12.0 is the current plugin and handles it.
mvn -Prelease verifypasses. After merge: move the unpublishedv0.3.0tag to the new main and the release workflow republishes (nothing reached Central, so no version is burned).