From 311ba773c2762d69079432a4264a4da69565e5a0 Mon Sep 17 00:00:00 2001
From: Graham Russell <graham@ham1.co.uk>
Date: Sun, 6 Sep 2026 10:38:59 +0000
Subject: [PATCH 1/2] Raise Maven version floor to 3.9.9 and bump gated plugins

Bumps maven-enforcer-plugin, maven-compiler-plugin, and
gmavenplus-plugin, which were previously held back by a stale
requireMavenVersion floor pinned to jitpack.io's old default Maven.
3.9.9 is confirmed via JitPack build logs to be fetched and used
correctly; other nearby versions were tried and did not fetch
reliably.
---
 pom.xml | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/pom.xml b/pom.xml
index 5bdd18ba..344a7f2a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -130,7 +130,7 @@
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-enforcer-plugin</artifactId>
-        <version>3.6.2</version>
+        <version>3.6.3</version>
         <executions>
           <execution>
             <id>enforce-maven</id>
@@ -140,8 +140,13 @@
             <configuration>
               <rules>
                 <requireMavenVersion>
-                  <!-- this is the version jitpack.io uses -->
-                  <version>3.6.2</version>
+                  <!--
+                    JitPack has no project Maven Wrapper or .sdkmanrc, so it fetches a Maven
+                    version to build with based on this rule - but that matching isn't reliable
+                    for every version. Only raise this once a fresh JitPack build log confirms
+                    the exact requested version was actually used.
+                  -->
+                  <version>3.9.9</version>
                 </requireMavenVersion>
               </rules>
             </configuration>
@@ -153,7 +158,7 @@
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-compiler-plugin</artifactId>
-        <version>3.15.0</version>
+        <version>3.16.0</version>
         <configuration>
           <source>25</source>
           <target>25</target>
@@ -164,7 +169,7 @@
       <plugin>
         <groupId>org.codehaus.gmavenplus</groupId>
         <artifactId>gmavenplus-plugin</artifactId>
-        <version>4.3.1</version>
+        <version>5.1.0</version>
         <configuration>
           <targetBytecode>25</targetBytecode>
         </configuration>

From 3055ab0e6386a15d44c6fbd26d1dd358c2369e05 Mon Sep 17 00:00:00 2001
From: Graham Russell <graham@ham1.co.uk>
Date: Sun, 6 Sep 2026 10:39:04 +0000
Subject: [PATCH 2/2] Remove .sdkmanrc

JitPack has no project Maven Wrapper, and build logs confirm it
downloads and builds with whatever Maven version the pom's enforcer
rule requires on its own, so pinning Java/Maven for it separately via
SDKMAN is no longer necessary.
---
 .sdkmanrc | 5 -----
 1 file changed, 5 deletions(-)
 delete mode 100644 .sdkmanrc

diff --git a/.sdkmanrc b/.sdkmanrc
deleted file mode 100644
index 9c3491ea..00000000
--- a/.sdkmanrc
+++ /dev/null
@@ -1,5 +0,0 @@
-# Used by JitPack's build (see jitpack.yml's `sdk env install`/`sdk env`) since
-# its build environment has SDKMAN pre-installed but not mise. Local dev uses
-# .mise.toml instead - keep both in sync.
-java=25.0.4-tem
-maven=3.9.16