#654: Enable automatic Maven Central deployment (#655)

Co-authored-by: Pieterjan Spoelders <[email protected]>

Author: kaklakariada

.github/workflows/ci-build.yml

@@ -0,0 +1,59 @@
+# Project Keeper 5.2.1, released 2025-06-06
+
+Code name: Auto-publish to Maven Central
+
+## Summary
+
+This release fixes an issue with the `release.yml` workflow that required manually publishing of Maven Central deployments. Maven Central Deployments no are done automatically during the release build without manual steps.
+
+## Bugfixes
+
+* #654: Fixed automatic Maven Central deployment
+
+## Dependency Updates
+
+### Project Keeper Core
+
+#### Compile Dependency Updates
+
+* Updated `com.exasol:project-keeper-shared-model-classes:5.2.0` to `5.2.1`
+
+#### Runtime Dependency Updates
+
+* Updated `com.exasol:project-keeper-java-project-crawler:5.2.0` to `5.2.1`
+
+#### Test Dependency Updates
+
+* Updated `com.exasol:project-keeper-shared-test-setup:5.2.0` to `5.2.1`
+
+### Project Keeper Command Line Interface
+
+#### Compile Dependency Updates
+
+* Updated `com.exasol:project-keeper-core:5.2.0` to `5.2.1`
+
+#### Test Dependency Updates
+
+* Updated `com.exasol:project-keeper-shared-test-setup:5.2.0` to `5.2.1`
+
+### Project Keeper Maven Plugin
+
+#### Compile Dependency Updates
+
+* Updated `com.exasol:project-keeper-core:5.2.0` to `5.2.1`
+
+### Project Keeper Java Project Crawler
+
+#### Compile Dependency Updates
+
+* Updated `com.exasol:project-keeper-shared-model-classes:5.2.0` to `5.2.1`
+
+#### Test Dependency Updates
+
+* Updated `com.exasol:project-keeper-shared-test-setup:5.2.0` to `5.2.1`
+
+### Project Keeper Shared Test Setup
+
+#### Compile Dependency Updates
+
+* Updated `com.exasol:project-keeper-shared-model-classes:5.2.0` to `5.2.1`

.github/workflows/release.yml

@@ -125,7 +125,6 @@ Maven plugin `central-publishing-maven-plugin` creates a bundle and uploads it t
 ```sh
 mvn clean deploy -Dgpg.skip=false -DskipTests \
   -Dcentral-publishing.deploymentName="Testing Deployment" \
-  -Dcentral-publishing.autoPublish=false \
   -Dcentral-publishing.skipPublishing=true
 ```
 
@@ -172,11 +171,10 @@ Then run the following command:
 
 ```sh
 mvn clean deploy -Dgpg.skip=false -DskipTests \
-  -Dcentral-publishing.deploymentName="Testing Deployment" \
-  -Dcentral-publishing.autoPublish=false
+  -Dcentral-publishing.deploymentName="Testing Deployment"
 ```
 
-**Important:** Make sure to specify argument `-Dcentral-publishing.autoPublish=false`. Without this option, the bundle will be published automatically.
+**Important:** Do not specify property `central-publishing.autoPublish` to use the default value `false`. This ensures that the bundle will **not** be published automatically.
 
 Then login to Maven Central Portal and go to the [deployments page](https://central.sonatype.com/publishing/deployments). Verify that your component was deployed successfully and has the expected content.
 

doc/changes/changelog.md

@@ -18,7 +18,7 @@
         </license>
     </licenses>
     <properties>
-        <revision>5.2.0</revision>
+        <revision>5.2.1</revision>
         <!-- Integration test ProjectKeeperMojoIT starts a Maven build which requires Java 17. -->
         <java.version>17</java.version>
         <maven.version>3.9.10</maven.version>

doc/changes/changes_5.2.1.md

@@ -212,7 +212,7 @@ private ElementBuilder properties(final Collection<ProjectKeeperModule> enabledM
         if (enabledModules.contains(MAVEN_CENTRAL)) {
             properties
                     .child(element("gpg.skip").text("true"))
-                    .child(element("central-publishing.autoPublish").text("true"))
+                    .child(element("central-publishing.autoPublish").text("false"))
                     .child(element("central-publishing.skipPublishing").text("false"))
                     // Other options for waitUntil: published, uploaded
                     .child(element("central-publishing.waitUntil").text("validated"))

doc/developer_guide/developer_guide.md

@@ -222,3 +222,4 @@ jobs:
     uses: ./.github/workflows/release.yml
     with:
       started-from-ci: true
+      maven-central-auto-publish: true

maven-project-crawler/pk_generated_parent.pom

@@ -213,3 +213,4 @@ jobs:
     uses: ./.github/workflows/release.yml
     with:
       started-from-ci: true
+      maven-central-auto-publish: true

parent-pom/pom.xml

@@ -8,6 +8,11 @@ on:
         type: boolean
         required: true
         default: false
+      maven-central-auto-publish:
+        description: "Automatically publish to Maven Central. Deactivate to manually publish at https://central.sonatype.com/publishing/deployments"
+        required: true
+        type: boolean
+        default: true
   workflow_dispatch:
     inputs:
       skip-maven-central:

project-keeper-cli/pk_generated_parent.pom

@@ -126,6 +126,16 @@ void testOmitTestExcludeTagsPropertyForNonRootPom() {
         assertThat(pom.getProperties().get("test.excludeTags"), nullValue());
     }
 
+    @Test
+    void testAddPropertiesForMavenCentralDeployment() {
+        final Model pom = runGeneration(List.of(ProjectKeeperModule.MAVEN_CENTRAL), null);
+        assertAll(() -> assertThat(pom.getProperties().get("central-publishing.autoPublish"), equalTo("false")),
+                () -> assertThat(pom.getProperties().get("central-publishing.skipPublishing"), equalTo("false")),
+                () -> assertThat(pom.getProperties().get("central-publishing.waitUntil"), equalTo("validated")),
+                () -> assertThat(pom.getProperties().get("central-publishing.deploymentName"),
+                        equalTo("Manual deployment of repo my-repo")));
+    }
+
     private Model runGeneration(final List<ProjectKeeperModule> modules, final ParentPomRef parentPomRef) {
         final String result = new PomFileGenerator().generatePomContent(modules, "com.example", "my-parent-pom",
                 "1.0.0", parentPomRef, new RepoInfo(TEST_REPO_NAME, TEST_REPO_LICENSE));