-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MJAR-310] - fixed toolchain version detection when toolchain paths contain white spaces #86
Conversation
…tain white spaces
c5ff576
to
f07ad8f
Compare
@jansohn - please look at comments in JIRA https://issues.apache.org/jira/browse/MJAR-310 |
Makes sense but there are already three year old PRs trying to revert the extra use of cmd.exe so I'm not keen on going down that route. I think it makes more sense to just use ProcessBuilder directly for such a simple task. |
I stand corrected and #87 actually does solve the issue with blanks in Windows paths. Totally unintuitive that it works by setter and not by constructor argument in my opinion. While digging into the code I also saw that it actually dismisses the shell wrapping if it detects a non-Windows OS which explains why this only occurred on Windows systems. Personally I would not rely on such an overly complex third library for such a simple use case but feel free to merge whatever PR you prefer. |
@michael-o - next issue with parsing command line 😄 |
It does not surprise me. I have been telling that this is broken for years. |
@jansohn thanks |
Switched to
ProcessBuilder
for JDK toolchain version detection as it actually correctly handles white spaces in the executable path compared to the plexus-utils dependency.