fix(ci): use property-based compiler release for core and CLI isolation

PROBLEM:
- Command-line -Dmaven.compiler.release=25 overrides ALL property values in POMs
- Previous fix using ${dotcms.cli.compiler.release} in CLI POM didn't work
- CLI still inherited global override, causing Quarkus/ASM bytecode errors

SOLUTION:
- Added dotcms.core.compiler.release property (default 11) in parent POM
- Core modules reference ${dotcms.core.compiler.release} via maven.compiler.release
- CLI modules reference ${dotcms.cli.compiler.release} (default 11) directly
- Changed action to pass -Ddotcms.core.compiler.release instead of -Dmaven.compiler.release

RESULT:
- Override with -Ddotcms.core.compiler.release=25 affects only core modules
- CLI always uses release=11 (Quarkus/GraalVM compatible)
- Single Maven reactor build, no module exclusions needed
- Maintains backward compatibility (both default to 11)

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

Author: spbolton

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

@@ -233,19 +233,19 @@ runs:
           DEFAULT_ARGS="$DEFAULT_ARGS -Pnative"
         fi
 
-        # Add Maven compiler release override flag
+        # Add Maven compiler release override flag for core modules
         # 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
+        # Note: Core modules use dotcms.core.compiler.release (default 11), CLI uses dotcms.cli.compiler.release (default 11) for Quarkus/GraalVM compatibility
         COMPILER_ARGS=""
         if [[ -n "${{ inputs.maven-compiler-release }}" ]]; then
           # Explicit release override takes precedence
-          COMPILER_ARGS="-Dmaven.compiler.release=${{ inputs.maven-compiler-release }}"
-          echo "Using explicit maven.compiler.release=${{ inputs.maven-compiler-release }}"
+          COMPILER_ARGS="-Ddotcms.core.compiler.release=${{ inputs.maven-compiler-release }}"
+          echo "Using explicit dotcms.core.compiler.release=${{ inputs.maven-compiler-release }}"
         elif [[ -n "${{ inputs.java-version }}" ]]; then
           # Default compiler release to match the overridden Java version
           JAVA_MAJOR=$(echo "${{ inputs.java-version }}" | grep -oE '^[0-9]+')
-          COMPILER_ARGS="-Dmaven.compiler.release=${JAVA_MAJOR}"
-          echo "Defaulting maven.compiler.release=${JAVA_MAJOR} to match java-version"
+          COMPILER_ARGS="-Ddotcms.core.compiler.release=${JAVA_MAJOR}"
+          echo "Defaulting dotcms.core.compiler.release=${JAVA_MAJOR} to match java-version"
         fi
 
         FINAL_ARGS=$(echo "$DEFAULT_ARGS $COMPILER_ARGS $MAVEN_ARGS" | tr ' ' '\n' | awk '!seen[$0]++' | tr '\n' ' ')

parent/pom.xml

@@ -26,7 +26,10 @@
          support new version default in environments/environment.properties and can be changed for local developer in
         environments/dev/user-dev.properties -->
         <!--suppress UnresolvedMavenProperty -->
-        <maven.compiler.release>11</maven.compiler.release>
+        <!-- Core modules compiler release - can be overridden via -Ddotcms.core.compiler.release
+             Defaults to 11 to maintain current bytecode compatibility -->
+        <dotcms.core.compiler.release>11</dotcms.core.compiler.release>
+        <maven.compiler.release>${dotcms.core.compiler.release}</maven.compiler.release>
         <maven.compiler.source>${maven.compiler.release}</maven.compiler.source>
         <maven.compiler.target>${maven.compiler.release}</maven.compiler.target>
         <maven.compiler.testSource>${maven.compiler.source}</maven.compiler.testSource>