Fix CI build failures by using correct JDK 17 path for script execution and adding missing dependencies.

- Updated `scripts/build-android-app.sh` to prioritize `JAVA17_HOME` for executing `PatchGradleFiles.java`, ensuring compatibility with Java 11+ source file execution feature.
- Added `xalan` and `serializer` dependencies to `maven/codenameone-maven-plugin/pom.xml` to resolve `ClassNotFoundException` during CSS compilation in archetype builds.

Author: google-labs-jules[bot]

maven/codenameone-maven-plugin/pom.xml

@@ -219,6 +219,17 @@
             <artifactId>maven-model</artifactId>
 
         </dependency>
+
+        <dependency>
+            <groupId>xalan</groupId>
+            <artifactId>xalan</artifactId>
+            <version>2.7.3</version>
+        </dependency>
+        <dependency>
+            <groupId>xalan</groupId>
+            <artifactId>serializer</artifactId>
+            <version>2.7.3</version>
+        </dependency>
     </dependencies>
 
     <build>

scripts/build-android-app.sh

@@ -131,7 +131,7 @@ if [ ! -f "$PATCH_GRADLE_SOURCE_PATH/$PATCH_GRADLE_MAIN_CLASS.java" ]; then
   exit 1
 fi
 
-PATCH_GRADLE_JAVA="${JDK_HOME:-$JAVA17_HOME}/bin/java"
+PATCH_GRADLE_JAVA="${JAVA17_HOME:-${JDK_HOME:-$JAVA_HOME}}/bin/java"
 if [ ! -x "$PATCH_GRADLE_JAVA" ]; then
   ba_log "JDK java binary missing at $PATCH_GRADLE_JAVA" >&2
   exit 1