[BUILDTOOLS-561] Unable to use mvn command with Maven installed in a folder which contains special characters on Windows Created: 21/Nov/20 Updated: 12/Jan/21 Resolved: 12/Jan/21 |
|
| Status: | Resolved |
| Project: | BuildTools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Zeker Zhayard | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | BuildTools, bug | ||
| Environment: |
Windows 10 20H2 Oracle JDK 1.8.0_271 |
||
| Version: | git-BuildTools-7fe9375-122 |
| Guidelines Read: | Yes |
| Description |
|
Steps to reproduce: 1. Install maven in a folder which contains special characters (whitespaces, parentheses, brackets, etc.). It can also be reproduced with only using mvn in git bash, but using mvn.cmd will not appear any exceptions. A possible way to fix it is to use mvn.cmd instead of using mvn when running on Windows, notice that "sh mvn.cmd" command won't work. |
| Comments |
| Comment by md_5 [ 12/Jan/21 ] |
|
Even when Maven is fixed, ./applyPatches.sh does not support special characters in the path. I am unsure what the issue is there |
| Comment by Zeker Zhayard [ 22/Nov/20 ] |
|
BuildTools only blocked its own path with special characters, but not blocked maven path. |
| Comment by md_5 [ 21/Nov/20 ] |
|
We already block some special characters like # and !, But I'm pretty sure spaces have no issue |