fix(ci): exclude rollbar-java-agent on JDKs older than 17

Author: buongarzoni

rollbar-java-agent/README.md

@@ -31,7 +31,10 @@ Exactly one event is recorded per connection, even when your code hits several o
 
 ## Requirements
 
-- Java 11 or higher
+- Java 11 or higher **to run** the agent
+- Java 17 or higher **to build** it from source — the shadow plugin that packages the fat JAR
+  requires a Java 17+ JVM, so on an older JDK the module is excluded from the build entirely and
+  `:rollbar-java-agent` tasks fail as unknown. The JAR it produces still targets Java 11.
 - `rollbar-java` on the application classpath (for `Rollbar.init(...)`)
 
 The agent bundles only ByteBuddy, under a relocated package name. It does **not** bundle the

settings.gradle.kts

@@ -68,8 +68,17 @@ if (isJava8 || isJava11) {
     include(":rollbar-android", ":examples:rollbar-android")
 }
 
-if (isJava8) {
-    println("Java 8 detected: excluding :rollbar-java-agent (requires Java 11+)")
+// The agent's own artifact targets Java 11+ (JavaCompile release = 11), but *building* it needs a
+// Java 17+ JVM: it is packaged by com.gradleup.shadow 9.x, whose plugin marker declares a JVM 17
+// runtime requirement, so on an older JVM the build fails while resolving the plugin classpath —
+// before any task runs. Shadow 9.x is not optional here (Byte Buddy 1.18 ships Java 24 class files
+// under META-INF/versions/24, which earlier shadow releases cannot read), and a Java toolchain does
+// not help because the plugin is resolved against the Gradle daemon's JVM, not the toolchain.
+//
+// So exclude the module on Java 8 and 11. The CI matrix still builds and tests it on 17, and the
+// release job runs on 17.
+if (JavaVersion.current() < JavaVersion.VERSION_17) {
+    println("Java ${JavaVersion.current()} detected: excluding :rollbar-java-agent (building it requires Java 17+)")
 } else {
     include(":rollbar-java-agent")
 }