Migrate to com.vanniktech.maven.publish for Maven Central

[AkaZver]

Summary

Migrate to the official com.vanniktech.maven.publish plugin for Maven Central publishing instead of manual curl-based configuration.

Changes

build.gradle

• Add com.vanniktech.maven.publish plugin version 0.37.0
• Remove maven-publish and signing plugins (no longer needed)
• Remove withJavadocJar() (plugin handles this automatically)
• Remove publishing and signing blocks (~50 lines)
• Add mavenPublishing block with configuration:
  • publishToMavenCentral(true) — automatic publishing
  • signAllPublications() — GPG signing
  • POM metadata with inceptionYear = '2021'

.github/workflows/main.yml

• Simplify publish-maven-central job
• Remove 4 steps: Publish to local repository, Create bundle, Verify bundle structure, Upload to Central Portal
• Add single step: Publish to Maven Central
• Use ORG_GRADLE_PROJECT_* environment variables for secrets

Benefits

• Less code: removed ~50 lines of manual configuration
• Reliability: using proven solution with 1.7k stars on GitHub
• Simplicity: single command ./gradlew publishToMavenCentral instead of complex curl workflow
• Automation: plugin handles validation, publishing, and status monitoring
• Official recommendation: Sonatype recommends this plugin in their documentation

Testing

• ./gradlew clean build — BUILD SUCCESSFUL
• Configuration is correct, all tests pass
• Secrets are passed via environment variables

Next Steps

After merging:

1. Create tag 2.0.3 to test new configuration
2. Verify publishing to Maven Central
3. Ensure artifacts appear on mvnrepository.com

[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