Describe the artifact in the POM - #124
Merged
Merged
Conversation
Sonatype Central rejects a deployment whose POM carries no name and no description; the 1.3.0 bundle failed validation on exactly that. Both fields were inherited from the parent before, which the portal does not accept.
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.
Sonatype Central rejected the 1.3.0 bundle: the POM carried neither
namenordescription, and the portal does not accept them by inheritance. plexus-io hit the same thing and fixed it the same way before its 3.7.0 release.Once this merges, 1.3.0 can be cut again — nothing from the failed attempt reached Central.
This change was created with AI assistance.