Skip to content

Add required Maven Central POM metadata#132

Merged
AhmedNMahran merged 1 commit intomainfrom
fix/add-maven-central-pom-metadata
Mar 10, 2026
Merged

Add required Maven Central POM metadata#132
AhmedNMahran merged 1 commit intomainfrom
fix/add-maven-central-pom-metadata

Conversation

@AhmedNMahran
Copy link
Collaborator

Summary

This adds the Maven Central POM metadata currently required by Central validation for all published artifacts.

What changed

  • added shared project metadata entries in gradle/libs.versions.toml for:
    • license
    • SCM connections
    • developer identity
  • updated all published modules to include the missing POM sections:
    • licenses
    • developers
    • scm

Updated modules:

  • auth
  • mutations-definitions
  • persistence
  • syncengine
  • sync-pipelines (mobile-sync)
  • umbrella

Why

Central validation reported the following metadata warnings/errors during publish:

  • License information is missing
  • SCM URL is not defined
  • Developers information is missing

These fields are required for Maven Central publication and need to be present on every published artifact.

Validation

Regenerated publication POMs successfully with:

./gradlew \
  :sync-pipelines:generatePomFileForKotlinMultiplatformPublication \
  :auth:generatePomFileForKotlinMultiplatformPublication \
  :persistence:generatePomFileForKotlinMultiplatformPublication \
  :syncengine:generatePomFileForKotlinMultiplatformPublication \
  :mutations-definitions:generatePomFileForKotlinMultiplatformPublication \
  --no-configuration-cache \
  --stacktrace

Verified generated POMs now include:

  • <licenses>
  • <developers>
  • <scm>

Note

The POM metadata now uses org-safe developer information:

  • id = quran
  • name = Quran Foundation

No personal email is included in the published metadata.

The license metadata is set to GPL-3.0 to match quran_android.

If mobile-sync is 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.

@AhmedNMahran AhmedNMahran self-assigned this Mar 10, 2026
@AhmedNMahran AhmedNMahran merged commit 1d8f5be into main Mar 10, 2026
1 check passed
@AhmedNMahran AhmedNMahran deleted the fix/add-maven-central-pom-metadata branch March 10, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant