From 97bc401225340216a5e930d97d20c1c6008bf7bf Mon Sep 17 00:00:00 2001
From: Jeremy Landis <jeremylandis@hotmail.com>
Date: Thu, 23 May 2024 12:53:59 -0400
Subject: [PATCH 1/2] [pom] Bump modernizer to 2.9.0

---
 pom.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pom.xml b/pom.xml
index b3ea6c09..7b03aa7b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -248,9 +248,9 @@
         <!-- Automatic Module Name -->
         <module.name>com.github.spotbugs.maven</module.name>
 
-        <!-- TODO: Drop modernizer back to 2.7.0 due to strict maven 3.9.5 requirement -->
-        <modernizer.version>2.7.0</modernizer.version>
-        <modernizer.plugin>2.7.0</modernizer.plugin>
+        <!-- TODO: Remove after base-parent 46 released -->
+        <modernizer.version>2.9.0</modernizer.version>
+        <modernizer.plugin>2.9.0</modernizer.plugin>
     </properties>
 
     <dependencyManagement>

From 0443045fb65091b8ea5da88008b38ae7534e76bf Mon Sep 17 00:00:00 2001
From: Jeremy Landis <jeremylandis@hotmail.com>
Date: Mon, 6 May 2024 13:13:50 -0400
Subject: [PATCH 2/2] [ci] Update readme for security manager

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0f59a76a..12550173 100644
--- a/README.md
+++ b/README.md
@@ -85,7 +85,7 @@ This plugin is written entirey in groovy.  It does have limitations when it come
 
 Known issues
 
-The security manager is turned off by default in jdk 18/19 and scheduled from removal in a future java release, therefore to use this plugin with jdk 18/19, the security manager may need turned back on using ```JAVA_OPTS``` to ```-Djava.security.manager=allow```.  See [groovy](https://groovy-lang.org/releasenotes/groovy-4.0.html) for more details.
+The security manager is turned off by default in jdk 18 and scheduled from removal in a future java release, therefore to use this plugin with jdk 18+, the security manager may need turned back on using ```JAVA_OPTS``` to ```-Djava.security.manager=allow```.  See [groovy](https://groovy-lang.org/releasenotes/groovy-4.0.html) for more details.
 
 If using groovy with same group id (```org.codehaus.groovy 3.x``` or before or ```org.apache.groovy 4.x or above```), an error may occur if not on same version. To alleviate that, make sure groovy artifacts are defined in ```dependency management``` in order to force the loaded version correctly on your usage.