From 4670a4bbfb143e526482e7258ebc3b604756f671 Mon Sep 17 00:00:00 2001
From: Sylwester Lachiewicz <slachiewicz@apache.org>
Date: Mon, 24 Aug 2026 20:35:57 +0200
Subject: [PATCH] Preview Apache RAT 0.18 on JDK 17 and newer

RAT 0.18 is Java 17 bytecode, and the shared CI matrix still runs a JDK 8 cell,
so the version moves only where the build JDK can load it. Everything else keeps
0.16.1 and is unaffected.

The profile is deliberately temporary: it exists to exercise 0.18 across the core
projects before the ASF parent adopts it, and it should be removed once that
lands. Do not extend it into a migration from <excludes> to <inputExcludes> --
the two are not equivalent. On this project the rename cut the scanned file count
from 28 to 4, dropping every sub-module, and still reported success.

Verified: JDK 25 -> 0.18, process-resources passes; JDK 11 -> 0.16.1, passes
---
 pom.xml | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/pom.xml b/pom.xml
index 0423c95..70cdcad 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1388,6 +1388,23 @@ under the License.</licenseText>
   </reporting>
 
   <profiles>
+    <!-- TEMPORARY: evaluate Apache RAT 0.18 across the core projects before the
+         ASF parent adopts it (apache/maven-apache-parent#587). RAT 0.18 is Java 17
+         bytecode, so it can only run where the build JDK is 17 or newer; the
+         shared CI matrix still includes a JDK 8 cell, which keeps 0.16.1.
+         Remove this profile once the ASF parent ships 0.18 and the JDK floor is
+         settled. Do NOT migrate <excludes> to <inputExcludes> here: the two are
+         not equivalent, and the rename silently stops scanning sub-modules. -->
+    <profile>
+      <id>rat-0.18-preview</id>
+      <activation>
+        <jdk>[17,)</jdk>
+      </activation>
+      <properties>
+        <version.apache-rat-plugin>0.18</version.apache-rat-plugin>
+      </properties>
+    </profile>
+
     <profile>
       <id>java17+</id>
       <activation>