Fix JLine module loading to eliminate native access warnings

Added --add-modules org.jline.terminal.ffm flag to ensure JLine modules are
properly loaded as named modules before applying --enable-native-access.
This eliminates the 'Unknown module' warnings that occurred when JLine
modules were loaded as automatic modules.

Key changes:
- Added --add-modules org.jline.terminal.ffm to both Unix and Windows launchers
- Moved MODULE_PATH definition earlier in scripts for version checking
- Now mvn --version runs without any native access warnings
- JLine FFM module is properly recognized for native access permissions

The implementation now provides clean JPMS module support with targeted
native access control and no warning messages.

Author: gnodet

apache-maven/src/assembly/maven/bin/mvn

@@ -107,7 +107,9 @@ else
   fi
 fi
 
-if ! "$JAVACMD" --enable-native-access=org.jline.terminal.ffm -version >/dev/null 2>&1; then
+MODULE_PATH="$MAVEN_HOME/modules"
+
+if ! "$JAVACMD" --module-path "$MODULE_PATH" --add-modules org.jline.terminal.ffm --enable-native-access=org.jline.terminal.ffm -version >/dev/null 2>&1; then
   echo "Error: Apache Maven 4.x requires Java 17 or newer to run." >&2
   "$JAVACMD" -version >&2
   echo "Please upgrade your Java installation or set JAVA_HOME to point to a compatible JDK." >&2
@@ -192,7 +194,6 @@ MAVEN_PROJECTBASEDIR="`find_maven_basedir "$@"`"
 MAVEN_OPTS="$MAVEN_OPTS `concat_lines "$MAVEN_PROJECTBASEDIR/.mvn/jvm.config"`"
 LAUNCHER_JAR=`echo "$MAVEN_HOME"/boot/maven-classworlds-*.jar`
 LAUNCHER_CLASS=org.codehaus.plexus.classworlds.launcher.Launcher
-MODULE_PATH="$MAVEN_HOME/modules"
 
 # For Cygwin and MinGW, switch paths to Windows format before running java(1) command
 if $cygwin || $mingw ; then
@@ -244,6 +245,7 @@ cmd="\"$JAVACMD\" \
   $MAVEN_OPTS \
   $MAVEN_DEBUG_OPTS \
   --module-path \"$MODULE_PATH\" \
+  --add-modules org.jline.terminal.ffm \
   --enable-native-access=org.jline.terminal.ffm \
   -classpath \"$LAUNCHER_JAR\" \
   \"-Dclassworlds.conf=$CLASSWORLDS_CONF\" \

apache-maven/src/assembly/maven/bin/mvn.cmd

@@ -74,8 +74,10 @@ if not exist "%JAVACMD%" (
   goto error
 )
 
+set MODULE_PATH="%MAVEN_HOME%\modules"
+
 @REM Check Java version by testing the Java 17+ flag
-"%JAVACMD%" --enable-native-access=org.jline.terminal.ffm -version >nul 2>&1
+"%JAVACMD%" --module-path %MODULE_PATH% --add-modules org.jline.terminal.ffm --enable-native-access=org.jline.terminal.ffm -version >nul 2>&1
 if ERRORLEVEL 1 (
     echo Error: Apache Maven 4.x requires Java 17 or newer to run. >&2
     "%JAVACMD%" -version >&2
@@ -249,7 +251,6 @@ call :processArgs %*
 
 for %%i in ("%MAVEN_HOME%"\boot\maven-classworlds-*) do set LAUNCHER_JAR="%%i"
 set LAUNCHER_CLASS=org.codehaus.plexus.classworlds.launcher.Launcher
-set MODULE_PATH="%MAVEN_HOME%\modules"
 if "%MAVEN_MAIN_CLASS%"=="" @set MAVEN_MAIN_CLASS=org.apache.maven.cling.MavenCling
 
 "%JAVACMD%" ^
@@ -258,6 +259,7 @@ if "%MAVEN_MAIN_CLASS%"=="" @set MAVEN_MAIN_CLASS=org.apache.maven.cling.MavenCl
   %JVM_CONFIG_MAVEN_OPTS% ^
   %MAVEN_DEBUG_OPTS% ^
   --module-path %MODULE_PATH% ^
+  --add-modules org.jline.terminal.ffm ^
   --enable-native-access=org.jline.terminal.ffm ^
   -classpath %LAUNCHER_JAR% ^
   "-Dclassworlds.conf=%CLASSWORLDS_CONF%" ^