Prepare version 0.12.0

Author: natario1

README.md

@@ -9,9 +9,12 @@
 A lightweight, handy Gradle plugin to deploy your maven packages (for example, Android AARs, Java JARs, Kotlin KLibs)
 to different kinds of repositories. It supports publishing to:
 - local directories, to use them as local maven repositories in other projects
-- Sonatype Nexus repositories, including [Sonatype OSSRH / Maven Central](https://central.sonatype.org/)
+- [Maven Central](https://central.sonatype.org/) repository via Sonatype's OSSRH
+- Other Sonatype Nexus repositories
 - [GitHub Packages](https://docs.github.com/en/packages)
 
+> For Maven Central builds, the plugin takes care of releasing the artifacts using Sonatype REST APIs so you don't have to use their web UI. 
+
 ```kotlin
 // settings.gradle.kts
 pluginManagement {
@@ -23,7 +26,7 @@ pluginManagement {
 
 // build.gradle.kts of deployable modules
 plugins {
-    id("io.deepmedia.tools.deployer") version "0.11.0"
+    id("io.deepmedia.tools.deployer") version "0.12.0"
 }
 ```
 

deployer/build.gradle.kts

@@ -46,7 +46,7 @@ gradlePlugin {
 }
 
 group = "io.deepmedia.tools.deployer"
-version = "0.12.0-rc1" // on change, update both docs and README
+version = "0.12.0" // on change, update both docs and README
 
 deployer {
     verbose = true

docs/index.mdx

@@ -13,5 +13,9 @@ docs:
 `MavenDeployer` is a lightweight, handy Gradle plugin to deploy your maven packages (for example, Android AARs, Java JARs, Kotlin KLibs)
 to different kinds of repositories. It supports publishing to:
 - local directories, to use them as local maven repositories in other projects
-- Sonatype Nexus repositories, including [Sonatype OSSRH / Maven Central](https://central.sonatype.org/)
+- [Maven Central](https://central.sonatype.org/) repository via Sonatype's OSSRH
+- Other Sonatype Nexus repositories
 - [GitHub Packages](https://docs.github.com/en/packages)
+
+> For Maven Central builds, the plugin takes care of releasing the artifacts using Sonatype REST APIs so you don't have to use their web UI.
+

docs/install.mdx

@@ -19,7 +19,7 @@ pluginManagement {
 
 // build.gradle.kts of deployable modules
 plugins {
-    id("io.deepmedia.tools.deployer") version "0.11.0"
+    id("io.deepmedia.tools.deployer") version "0.12.0"
 }
 ```
 

docs/repos/index.mdx

@@ -14,5 +14,5 @@ exposed through subclasses of the `DeploySpec` type, so that, for example, a `lo
 
 `MavenDeployer` supports publishing to:
 - local directories, to use them as local maven repositories in other projects [[docs](local)]
-- Sonatype Nexus repositories, including [Sonatype OSSRH / Maven Central](https://central.sonatype.org/) [[docs](sonatype)]
+- Sonatype Nexus repositories, with support for syncing to [Maven Central](https://central.sonatype.org/) [[docs](sonatype)]
 - [GitHub Packages](https://docs.github.com/en/packages) [[docs](github)]

docs/repos/sonatype.mdx

@@ -4,33 +4,24 @@ title: Sonatype & Maven Central
 
 # Sonatype & Maven Central
 
-Add a new spec with `sonatypeSpec {}`. It adds a mandatory property called `repositoryUrl`, which is the remote URL
-of the sonatype repo. This defaults to `https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/` -
-the Sonatype OSSRH which can be synced to Maven Central.
-
-Sonatype repositories make many fields mandatory:
-- authentication: use the `auth` block as shown below
-- signing
-- valid project url and scm
-- at least one developer and a license
-- possibly more
-
-Deployment will fail with clear errors notifying you about what's missing.
+Add a new spec with `sonatypeSpec {}` or `nexusSpec {}`. It adds a mandatory property called `repositoryUrl`, which is the remote URL
+of the sonatype repo. This defaults to `https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/`, one of the
+OSSRH urls that can be synced to Maven Central.
 
 ```kotlin
 deployer {
     // Common configuration...
     project.description.set("Handy tool to publish maven packages in different repositories.")
 
     sonatypeSpec {
-        // Sonatype configuration...
+        // Target URL. You can use `ossrh`, `ossrh1`, `ossrhSnapshots`, `ossrhSnapshots1` or your own URL
         repositoryUrl.set(ossrh1)
 
-        // Credentials used to register the package group into the OSSRH repository...
+        // For OSSRH projects, these are the credentials that were used to register the package group into OSSRH
         auth.user.set(secret("SONATYPE_USER"))
         auth.password.set(secret("SONATYPE_PASSWORD"))
 
-        // Signing is required
+        // Note: signing is required for Maven Central sync
         signing.key.set(secret("SIGNING_KEY"))
         signing.password.set(secret("SIGNING_PASSWORD"))
     }
@@ -43,3 +34,36 @@ deployer {
     }
 }
 ```
+
+## Maven Central sync
+
+Sonatype's OSSRH projects are allowed to sync artifacts with the [Maven Central](https://central.sonatype.org/) repository.
+The process is generally tricky, because you have to:
+
+- Build maven packages with a very strict set of rules (for example, signing is mandatory)
+- Deploy them to `oss.sonatype.org/service/local/staging/deploy/maven2` or `s01.oss.sonatype.org/service/local/staging/deploy/maven2`
+- Access the web interface at `oss.sonatype.org` or `s01.oss.sonatype.org`
+- Login with your credentials
+- Find the staging repository corresponding to the upload, `Close` it and then `Release` it
+
+Deployer streamlines the process so that only the first step is really your responsibility.
+First, enable maven central sync using `syncToMavenCentral`:
+
+```kotlin
+sonatypeSpec {
+    syncToMavenCentral = true
+
+    auth.user = secret("SONATYPE_USER")
+    auth.password = secret("SONATYPE_PASSWORD")
+}
+```
+
+Then simply run the deploy task. Deployer will:
+
+- Validate your artifacts and POM file, to ensure they won't be rejected by the backend
+- Fail with clear errors if any issue is found
+- Use Sonatype's REST APIs to create a staging repository in your Sonatype account
+- Upload the artifacts
+- Use Sonatype's REST APIs to close and release the staging repository
+
+