From 3f8dc01ca0ee53312eb295885b891222dc5d5cb3 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 13 Aug 2026 05:54:30 +0000 Subject: [PATCH] Stop nexus-staging hijacking the deploy phase The plugin declared true, which replaces the deploy lifecycle: the goal that ran was injected-nexus-deploy, never maven-deploy-plugin. For a release version it performed the OSSRH staging workflow and required a server credential with ID "ossrh". Nothing defines one, and nothing should -- distributionManagement points at GitHub Packages. So no non-SNAPSHOT version could publish. 2.16.0 failed on the parent pom with both library modules skipped, and nothing was uploaded. A SNAPSHOT version took a bulk-deploy path instead, which is why every successful publish in this repository's history has been a SNAPSHOT and the bug went unnoticed since 2.5.4-snapshot. Removing the plugin lets maven-deploy-plugin handle deploy and honour distributionManagement. Verified against a local file repository at both a SNAPSHOT and a release version: all three artifacts deploy, the parent pom included, which consumers resolving cfml.parsing cannot do without. The four trailing Sonatype comments go too -- they document a publishing route this project does not use. Closes #58 --- pom.xml | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/pom.xml b/pom.xml index fe23083..a016f63 100644 --- a/pom.xml +++ b/pom.xml @@ -202,17 +202,6 @@ - - org.sonatype.plugins - nexus-staging-maven-plugin - 1.7.0 - true - - ossrh - https://oss.sonatype.org/ - false - - @@ -253,10 +242,6 @@ - - - - github