#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?
performancecopilot · Nov 29, 2024 · 4da550f · 4da550f
1 parent 3f537f9
commit 4da550f
Showing 1 changed file with 13 additions and 0 deletions.
diff --git 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>