From 4da550ff82609ffd6f69e0a72e5b7c7ea44a4831 Mon Sep 17 00:00:00 2001
From: Paul Smith <tallpsmith@gmail.com>
Date: Fri, 29 Nov 2024 11:55:16 +1100
Subject: [PATCH] #130 Modifications to the new suggested Maven release
 process.

My suspciion is with some previous pom refactoring we were missing the configured Release profile trigger which generated important stuff for the deploy, probably rejecting the artifacts somewhere?
---
 pom.xml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/pom.xml b/pom.xml
index 30005dd..2431140 100644
--- a/pom.xml
+++ b/pom.xml
@@ -131,9 +131,22 @@
                     <configuration>
                         <mavenExecutorId>forked-path</mavenExecutorId>
                         <autoVersionSubmodules>true</autoVersionSubmodules>
+                        <useReleaseProfile>false</useReleaseProfile>
+                        <releaseProfiles>sonatype-release-profile</releaseProfiles>
                         <tagNameFormat>@{project.version}</tagNameFormat>
                     </configuration>
                 </plugin>
+                <plugin>
+                    <groupId>org.sonatype.plugins</groupId>
+                    <artifactId>nexus-staging-maven-plugin</artifactId>
+                    <version>1.6.7</version>
+                    <extensions>true</extensions>
+                    <configuration>
+                        <serverId>sonatype-nexus-staging</serverId>
+                        <nexusUrl>https://oss.sonatype.org/</nexusUrl>
+                        <autoReleaseAfterClose>false</autoReleaseAfterClose>
+                    </configuration>
+                </plugin>
             </plugins>
         </pluginManagement>
         <plugins>