From 26d559e5c25dc21736b7df6b345eaec7ed04604d Mon Sep 17 00:00:00 2001
From: Michael Bayne <mdb@samskivert.com>
Date: Tue, 24 May 2022 10:24:58 -0700
Subject: [PATCH] Upgrade Proguard to a version that supports Java 18.

For unfortunate reasons, we have to add a separate (build-time) dependency on
proguard-core, code from which proguard-base relies on but neither includes
directly nor expresses as a dependency.

How is it in the year of our lord two thousand and twenty two, we are still
making such basic build errors in our Maven plugins and POM files?
---
 launcher/pom.xml | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/launcher/pom.xml b/launcher/pom.xml
index e61c1db..5b4ffc8 100644
--- a/launcher/pom.xml
+++ b/launcher/pom.xml
@@ -85,7 +85,7 @@
       <plugin>
         <groupId>com.github.wvengen</groupId>
         <artifactId>proguard-maven-plugin</artifactId>
-        <version>2.3.1</version>
+        <version>2.5.1</version>
         <executions>
           <execution>
             <phase>package</phase>
@@ -96,12 +96,18 @@
           <dependency>
             <groupId>com.guardsquare</groupId>
             <artifactId>proguard-base</artifactId>
-            <version>7.0.0</version>
+            <version>7.2.1</version>
+            <scope>runtime</scope>
+          </dependency>
+          <dependency>
+            <groupId>com.guardsquare</groupId>
+            <artifactId>proguard-core</artifactId>
+            <version>9.0.0</version>
             <scope>runtime</scope>
           </dependency>
         </dependencies>
         <configuration>
-          <proguardVersion>7.0.0</proguardVersion>
+          <proguardVersion>7.2.1</proguardVersion>
           <outputDirectory>${project.build.directory}</outputDirectory>
           <outjar>${project.build.finalName}.jar</outjar>
           <injar>${project.build.finalName}.jar</injar>