From 075a10b5c26b01ddfe8685bf2c63f1c8d9ff70dd Mon Sep 17 00:00:00 2001
From: Pradeep Daniel <pradeep.samuel90@gmail.com>
Date: Sun, 26 Jul 2026 22:47:35 +0530
Subject: [PATCH] Resolve Gumbo from JitPack instead of a hand-built local
 install
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Catalyst depended on com.cajunsystems:gumbo, which is the coordinate Gumbo's
own pom declares and not the one anybody can actually fetch. JitPack rewrites
the groupId to com.github.{owner} when it publishes, so the same jar is
com.github.CajunSystems:gumbo once it leaves the build that made it. The
practical consequence is that this build resolved only on a machine where
someone had run `mvn install` on a Gumbo checkout by hand, and failed
everywhere else — including on a clean clone — with a message that points at
Maven Central rather than at the actual cause:

    Could not find artifact com.cajunsystems:gumbo:jar:0.3.0 in central

That was measured here, not inferred: the build fails that way before this
change, and after it Maven downloads
com/github/CajunSystems/gumbo/0.3.0/gumbo-0.3.0.jar from jitpack.io and the
full reactor compiles — 11 modules SUCCESS, catalyst-gumbo's own tests 9/9,
with nothing installed locally.

The comment this replaces said jitpack.io was blocked by egress policy and
that Gumbo therefore had to come from the local repository. That was true of
one sandboxed environment, not of the delivery mechanism, and it had hardened
into a property of the build. jitpack.io answers normally from a machine with
ordinary network access. The new comment explains why two coordinates exist
at all, so the next reader does not "correct" this back to the one in Gumbo's
pom.

Version stays 0.3.0. Gumbo 0.4.0 is cut but not yet tagged, so it is not on
JitPack; bumping is a separate change once it is.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 catalyst-gumbo/pom.xml |  2 +-
 pom.xml                | 27 ++++++++++++++++++++-------
 2 files changed, 21 insertions(+), 8 deletions(-)

diff --git a/catalyst-gumbo/pom.xml b/catalyst-gumbo/pom.xml
index 95bf023..4b721a0 100644
--- a/catalyst-gumbo/pom.xml
+++ b/catalyst-gumbo/pom.xml
@@ -24,7 +24,7 @@
             <artifactId>catalyst-events</artifactId>
         </dependency>
         <dependency>
-            <groupId>com.cajunsystems</groupId>
+            <groupId>com.github.CajunSystems</groupId>
             <artifactId>gumbo</artifactId>
         </dependency>
         <dependency>
diff --git a/pom.xml b/pom.xml
index de79f7f..f72e452 100644
--- a/pom.xml
+++ b/pom.xml
@@ -42,14 +42,27 @@
     </properties>
 
     <!--
-      Gumbo (com.cajunsystems:gumbo:0.3.0) is the durable log backend. The intended delivery was
-      JitPack, but jitpack.io is blocked by this environment's egress policy, so Gumbo is resolved
-      from the local Maven repository instead: build it once with
-          mvn -f /path/to/gumbo/pom.xml install -DskipTests
-      which installs com.cajunsystems:gumbo:0.3.0 into ~/.m2. Its own dependencies resolve from
-      Maven Central. No Gumbo source is vendored into this build.
+      Gumbo is the durable log backend, delivered by JitPack, which builds it from the tag in
+      the CajunSystems/gumbo repository.
+
+      The coordinate is com.github.CajunSystems:gumbo, not the com.cajunsystems:gumbo that
+      Gumbo's own pom declares. JitPack rewrites the groupId to com.github.{owner} when it
+      publishes, so the string that resolves depends on where the jar came from: build Gumbo
+      locally with `mvn install` and it lands in ~/.m2 as com.cajunsystems:gumbo; fetch the
+      same jar from JitPack and it is com.github.CajunSystems:gumbo. This build uses the
+      JitPack one, so it resolves on any machine with network access rather than only on one
+      where Gumbo has been built by hand.
+
+      No Gumbo source is vendored into this build; its own dependencies resolve from Central.
     -->
 
+    <repositories>
+        <repository>
+            <id>jitpack.io</id>
+            <url>https://jitpack.io</url>
+        </repository>
+    </repositories>
+
     <dependencyManagement>
         <dependencies>
             <!-- Internal modules -->
@@ -135,7 +148,7 @@
                 <version>${bytebuddy.version}</version>
             </dependency>
             <dependency>
-                <groupId>com.cajunsystems</groupId>
+                <groupId>com.github.CajunSystems</groupId>
                 <artifactId>gumbo</artifactId>
                 <version>${gumbo.version}</version>
                 <exclusions>