fix(ci): use property-based compiler release for CLI modules

Replace CLI module exclusion approach with a cleaner property-based
isolation strategy.

Changes:
- Add dotcms.cli.compiler.release property in parent/pom.xml (defaults to 21)
- CLI module POM now uses ${dotcms.cli.compiler.release} instead of hardcoded 11
- Remove CLI exclusion logic from maven-job action

This allows:
- Global maven.compiler.release can be set to any version (e.g., 25)
- CLI modules always compile with safe bytecode version (21) for Quarkus/GraalVM
- Single Maven reactor build (no exclusions or multi-pass)
- Clean property-based separation of concerns

Example usage:
  ./mvnw clean install -Dmaven.compiler.release=25
  # Main modules: Java 25 bytecode
  # CLI modules: Java 21 bytecode (Quarkus compatible)

This resolves ASM limitation:
  java.lang.IllegalArgumentException: Unsupported class file major version 69

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: spbolton

.github/actions/core-cicd/maven-job/action.yml

@@ -233,15 +233,9 @@ runs:
           DEFAULT_ARGS="$DEFAULT_ARGS -Pnative"
         fi
 
-        # Skip CLI modules when java-version is overridden (Quarkus/GraalVM compatibility)
-        CLI_EXCLUSION=""
-        if [[ -n "${{ inputs.java-version }}" ]]; then
-          CLI_EXCLUSION="-pl '!:dotcms-cli-parent,!:dotcms-api-data-model,!:dotcms-cli'"
-          echo "Excluding CLI modules due to java-version override (Quarkus/GraalVM compatibility)"
-        fi
-
         # Add Maven compiler release override flag
         # Priority: explicit maven-compiler-release > default from java-version major > project defaults
+        # Note: CLI modules use dotcms.cli.compiler.release property (hardcoded to 21) for Quarkus/GraalVM compatibility
         COMPILER_ARGS=""
         if [[ -n "${{ inputs.maven-compiler-release }}" ]]; then
           # Explicit release override takes precedence
@@ -254,7 +248,7 @@ runs:
           echo "Defaulting maven.compiler.release=${JAVA_MAJOR} to match java-version"
         fi
 
-        FINAL_ARGS=$(echo "$DEFAULT_ARGS $CLI_EXCLUSION $COMPILER_ARGS $MAVEN_ARGS" | tr ' ' '\n' | awk '!seen[$0]++' | tr '\n' ' ')
+        FINAL_ARGS=$(echo "$DEFAULT_ARGS $COMPILER_ARGS $MAVEN_ARGS" | tr ' ' '\n' | awk '!seen[$0]++' | tr '\n' ' ')
 
         if [[ "${{ runner.os }}" == "Windows" && "${{ inputs.native }}" == "true" ]]; then
           echo "Building Maven with args $FINAL_ARGS"

parent/pom.xml

@@ -31,6 +31,10 @@
         <maven.compiler.target>${maven.compiler.release}</maven.compiler.target>
         <maven.compiler.testSource>${maven.compiler.source}</maven.compiler.testSource>
         <maven.compiler.testTarget>${maven.compiler.target}</maven.compiler.testTarget>
+
+        <!-- CLI modules compiler release - separate property to support Java version override testing
+             Defaults to 21 for Quarkus/GraalVM compatibility (max supported by ASM in Quarkus 3.6.0) -->
+        <dotcms.cli.compiler.release>21</dotcms.cli.compiler.release>
         <java.module.args>
             --add-modules java.se,jdk.management.agent
             --add-exports java.base/jdk.internal.ref=ALL-UNNAMED

tools/dotcms-cli/pom.xml

@@ -24,9 +24,11 @@
     <quarkus.platform.version>3.6.0</quarkus.platform.version>
     <jreleaser-plugin.version>1.8.0</jreleaser-plugin.version>
     <google.findbugs.version>3.0.2</google.findbugs.version>
-      <maven.compiler.release>11</maven.compiler.release>
-      <maven.compiler.source>11</maven.compiler.source>
-      <maven.compiler.target>11</maven.compiler.target>
+      <!-- Use dedicated CLI compiler release property for Quarkus/GraalVM compatibility
+           This isolates CLI from global maven.compiler.release overrides -->
+      <maven.compiler.release>${dotcms.cli.compiler.release}</maven.compiler.release>
+      <maven.compiler.source>${dotcms.cli.compiler.release}</maven.compiler.source>
+      <maven.compiler.target>${dotcms.cli.compiler.release}</maven.compiler.target>
 
   </properties>