chore: add Maven Central metadata to pom.xml#6
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
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.
Purpose
The Sonatype Central portal shows "Let's write down a good description for this version!" because the published POM is missing standard Maven metadata fields. These fields are also required by Maven Central's validation rules.
What Changed
<name>— display name shown in package registries<description>— package description shown on central.sonatype.com and Maven Central<url>— link to the GitHub repository<licenses>— MIT licence declaration (required by Maven Central)<developers>— Rhesis AI as the developer (required by Maven Central)<scm>— source control metadata (required by Maven Central)<packaging>jar</packaging>— explicit packaging typeAdditional Context
These fields take effect from the next published release onwards. Version 0.1.4 already on Central cannot be retroactively edited, but all future releases will carry the description.
Testing
No code changes — verify by running
mvn validatelocally to confirm the POM parses correctly.