[ https://issues.apache.org/jira/browse/MNG-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MNG-8315: -------------------------------- Summary: Failure of mvn.cmd if a .mvn directory is located at drive root (was: Failure of mvn.cmd if a .mvn folder is located at drive root) > Failure of mvn.cmd if a .mvn directory is located at drive root > --------------------------------------------------------------- > > Key: MNG-8315 > URL: https://issues.apache.org/jira/browse/MNG-8315 > Project: Maven > Issue Type: Bug > Components: Command Line > Affects Versions: 3.9.9 > Environment: Windows 10 > Reporter: Francois MAROT > Priority: Minor > Labels: easyfix > > When .mvn is located on filesystem root, on Windows, the command line created > (in mvn.cmd) to run java fails. > This is because the part concerning multiModuleProjectDirectory ends with a > slash before the double quote which certainly means escaping and it messes > the whole command. Example for drive o: : > "-Dmaven.multiModuleProjectDirectory=o:\" > In this case, java.exe displays its usage help as it thinks the command is > wrong. > The workaround is to add an additional escaping backslash: > "-Dmaven.multiModuleProjectDirectory=o:" > Note: this only happens in case there is a .mvn at root. > > This simple line added just before calling "%JAVACMD%" seems to do the job: > if "{_}%MAVEN_PROJECTBASEDIR:~-1%"=="{_}\" set > "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\" > > -- This message was sent by Atlassian Jira (v8.20.10#820010)