Add required Maven Central POM metadata#132
Merged
AhmedNMahran merged 1 commit intomainfrom Mar 10, 2026
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.
Summary
This adds the Maven Central POM metadata currently required by Central validation for all published artifacts.
What changed
gradle/libs.versions.tomlfor:licensesdevelopersscmUpdated modules:
authmutations-definitionspersistencesyncenginesync-pipelines(mobile-sync)umbrellaWhy
Central validation reported the following metadata warnings/errors during publish:
License information is missingSCM URL is not definedDevelopers information is missingThese fields are required for Maven Central publication and need to be present on every published artifact.
Validation
Regenerated publication POMs successfully with:
Verified generated POMs now include:
<licenses><developers><scm>Note
The POM metadata now uses org-safe developer information:
id = quranname = Quran FoundationNo personal email is included in the published metadata.
The license metadata is set to GPL-3.0 to match
quran_android.If
mobile-syncis intended to use a different license, that should be corrected before the first successful Central release so the published metadata matches the actual project licensing.