Action for uploading lib to Maven Central

[fabiogouw]

Summary

This PR prepares spark-aws-messaging for Maven Central publication using Gradle and JReleaser.

What changed

• configured the library module to stage Maven artifacts locally and deploy them through JReleaser
• added a dedicated publishToMavenCentral task that chains staging and deployment
• wired Maven Central credentials and GPG signing material through environment variables only
• enabled JReleaser gitRootSearch and configured the com.fabiogouw namespace
• removed the placeholder spark-aws-messaging/jreleaser.yml so the Gradle-based release configuration is the single source of truth
• added a tag-driven GitHub Actions workflow for Maven Central upload
• changed the GitHub Actions release flow to upload only, leaving final publication approval to the Maven Central Portal
• simplified the existing CI workflow by removing obsolete OSSRH placeholder properties
• documented the release flow in README.md

Local deployment

Before running a release locally, export these environment variables:

• GITHUB_TOKEN
• MAVEN_CENTRAL_USERNAME
• MAVEN_CENTRAL_PASSWORD
• JRELEASER_GPG_SECRET_KEY
• JRELEASER_GPG_PASSPHRASE

Then run:

./gradlew :spark-aws-messaging:publishToMavenCentral

Useful validation commands:

./gradlew :spark-aws-messaging:jreleaserConfig
./gradlew :spark-aws-messaging:publishAllPublicationsToStagingRepository

If you want a two-step flow with manual confirmation in the Central Portal, use upload-only mode:

JRELEASER_MAVENCENTRAL_STAGE=UPLOAD ./gradlew :spark-aws-messaging:publishToMavenCentral

After the upload, review the deployment in the Maven Central Portal and confirm publication there.

GitHub Actions deployment

The release workflow is triggered by pushing a tag that matches v*.

Required GitHub Actions secrets:

• MAVEN_CENTRAL_USERNAME
• MAVEN_CENTRAL_PASSWORD
• JRELEASER_GPG_SECRET_KEY
• JRELEASER_GPG_PASSPHRASE

GITHUB_TOKEN is provided automatically by GitHub Actions.

Example release flow:

git tag v1.2.1
git push origin v1.2.1

The workflow uploads the deployment to Maven Central with JRELEASER_MAVENCENTRAL_STAGE=UPLOAD and stores JReleaser metadata as a workflow artifact. Final publication must then be confirmed manually in the Maven Central Portal.

Notes

• keep the Gradle version in spark-aws-messaging/build.gradle aligned with the Git tag
• if Maven Central provides token-based publishing credentials, use that generated username/password pair in MAVEN_CENTRAL_USERNAME and MAVEN_CENTRAL_PASSWORD

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud