From 46a87cc4d9bb6f76affd8fd92ff662c5c0a11994 Mon Sep 17 00:00:00 2001
From: gwr0-0 <wanrui.gao@outlook.com>
Date: Wed, 11 Nov 2026 17:12:13 +0800
Subject: [PATCH] build: drop the stale distributionManagement

central-publishing-maven-plugin publishes through its publishingServerId.
With -Pci,gpg, its extensions=true lifecycle participant clears
maven-deploy-plugin's execution and injects the Central publish goal, so
release deploys never read <distributionManagement>.

Snapshot deploys are unchanged: before this change the plugin used the
POM's <snapshotRepository>; after it falls back to the Central snapshots
repository, with the same URL and server id (central).

The block was also a trap: adding <site> would only change
release:perform's goals when <goals> is unset, and this POM pins
<goals>deploy</goals>.
---
 pom.xml | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/pom.xml b/pom.xml
index 615c1f523b..f42f19322b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -293,14 +293,4 @@
 		</repository>
 	</repositories>
 
-	<distributionManagement>
-		<snapshotRepository>
-			<id>central</id>
-			<url>https://central.sonatype.com/repository/maven-snapshots/</url>
-		</snapshotRepository>
-		<repository>
-			<id>central</id>
-			<url>https://central.sonatype.com/</url>
-		</repository>
-	</distributionManagement>
 </project>