From 58eb4251b83e65b2808a26275c2c6e7a8313fdf2 Mon Sep 17 00:00:00 2001
From: TestingBot <info@testingbot.com>
Date: Wed, 15 Jul 2026 19:24:18 +0200
Subject: [PATCH] Keep runtime deps in published POM; auto-publish to Maven
 Central

Two fixes to how the artifact is published:

1. createDependencyReducedPom=false: with the uber jar attached as the 'shaded' classifier,
   maven-shade-plugin's default dependency-reduced POM stripped every dependency that was shaded
   into the uber jar (Jetty, Apache HTTP, commons-cli, Jackson, ...). That left the published thin
   main jar declaring only test-scoped deps, so consumers got a jar with no resolvable runtime
   dependencies. Keep the full dependency list in the published POM.

2. autoPublish=true + waitUntil=published: the central-publishing-maven-plugin defaulted to a manual
   release, so 'mvn deploy' only uploaded a *pending* deployment that then had to be released by hand
   in the Central Portal (which is why 4.8 built green but never appeared on Maven Central). Now a
   deploy from either release.yml (on tag) or the manual Publish workflow actually publishes.
---
 pom.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/pom.xml b/pom.xml
index 94edf6a..998cdcc 100644
--- a/pom.xml
+++ b/pom.xml
@@ -77,6 +77,10 @@
         <extensions>true</extensions>
         <configuration>
           <publishingServerId>central</publishingServerId>
+          <!-- Actually release to Maven Central instead of leaving the deployment in a
+               "pending/validated" state that needs a manual "Publish" click in the portal. -->
+          <autoPublish>true</autoPublish>
+          <waitUntil>published</waitUntil>
         </configuration>
       </plugin>
       <plugin>
@@ -152,6 +156,11 @@
                    The runnable uber jar is attached under the "shaded" classifier for CLI/Docker use. -->
               <shadedArtifactAttached>true</shadedArtifactAttached>
               <shadedClassifierName>shaded</shadedClassifierName>
+              <!-- Keep the real dependencies in the published POM. Because the uber jar is only an
+                   attached artifact (not the main one), the main jar is thin and its consumers must
+                   resolve Jetty/HTTP/commons-cli/etc. transitively; the default dependency-reduced
+                   POM would strip exactly those and leave consumers with unresolvable classes. -->
+              <createDependencyReducedPom>false</createDependencyReducedPom>
               <minimizeJar>true</minimizeJar>
               <filters>
                 <filter>