Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.5.0
-
None
-
Windows 10 with PowerShell
Description
Executing maven on Windows using the -f or --file parameter to specify an alternate POM file can break the script if the path contains special characters.
It was originally discovered on a Windows Jenkins instance with working directory located under C:\Program Files (x86)\Jenkins......
Example:
mvn -f "folderWithClosing)Bracket/pomFolder"
Command line output: "Bracket/pomFolder" kann syntaktisch an dieser Stelle nicht verarbeitet werden.
Just for fun: Starting calc from maven script using -f
mvn -f " ' & start calc"
Command line output: POM file ' and a new calculator process
The bug was introduced with commit https://github.com/apache/maven/commit/f8ab2a650f32d5d87126d341d9bbfccbf99fd0ca for issue MNG-5889.
Workaround: Use maven 3.3.9 or below
Possible fix: Escape %FILE_ARG% and %POM_DIR% with " in echo commands in maven.cmd (line 120 and 129).
Attachments
Issue Links
- Blocked
-
MNG-6350 Maven 3.5.2 Command Line mvn.cmd fails on path names containing round bracket "()" chars
- Closed
- is duplicated by
-
MNG-6346 ... was unexpected at this time when using -f option and path contains brackets
- Closed
-
MNG-6350 Maven 3.5.2 Command Line mvn.cmd fails on path names containing round bracket "()" chars
- Closed
- is related to
-
MNG-5889 .mvn directory should be picked when using --file
- Closed
- relates to
-
MNG-6385 Windows mvn.cmd fail with incorrect command syntax.
- Open
- links to