gnodet commented on issue #7474: URL: https://github.com/apache/maven/issues/7474#issuecomment-4110310351
This issue is fixed in Maven 4. The `mvn.cmd` script has been completely rewritten with proper handling for: 1. **Paths with spaces**: All path variables (`MAVEN_HOME`, `JAVACMD`, `CLASSWORLDS_CONF`, etc.) are properly quoted throughout the script 2. **Argument parsing**: The `processArgs` subroutine uses `call :handleArgs %1` with proper argument forwarding, and the final Java invocation uses `%*` which preserves original quoting 3. **jvm.config parsing**: A dedicated Java-based `JvmConfigParser` was introduced to handle `.mvn/jvm.config` files with special characters, spaces, and quotes — avoiding batch script parsing pitfalls entirely (commits `6c191d03ca`, `9de4237b62`, `335ba3941c`) 4. **MAVEN_ARGS handling**: The Java-side `parseArguments()` method now properly handles quoted strings in `MAVEN_ARGS` (PR #11824) The original issue's scenario (paths containing spaces causing syntax errors) no longer reproduces with Maven 4's rewritten script. _Claude Code on behalf of Guillaume Nodet_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
