-
Notifications
You must be signed in to change notification settings - Fork 38
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
Java Classpath Broken #207
Comments
Just tried with a fresh install & the problem is the same. |
I can not suggest any proper solution but I have seen in many projects that a batch file is used to set the classpath. For example, I run batch scripts from jadx, ghidra etc. |
Could you enclose the |
@dscho This does indeed fix it. Is there something I can configure to force it to use |
That would be detrimental. The idea of MSYS2's path conversion is to guess how to handle command-line arguments passed between MSYS and non-MSYS programs. Since this is an ambiguous task, the heuristic is necessarily wrong at times. In your case, I think that the heuristic would have been correct if the second path element had been an absolute path. |
Something must have changed with a recent update because it used to parse the classpath parameter correctly without the need to enclose it in a call to |
@AntumDeluge commented 1 hour ago:
It would be nice if JRE for Windows would be taught to understand both Windows and *nix path formats. @AntumDeluge, in the meantime you could use some |
Yes, that sounds like a good solution. I said before that I didn't want to put it in a script [that was dedicated to a single command]. But that was nonsense, because putting it in a universal wrapper will do exactly what I want. |
I recently did a full upgrade
pacman -Syyu
& now I can't pass a classpath value to my Java virtual machine:It was working the last time that I had run the command a couple days ago, before I did the update today. Note that it had probably been months since I did a system upgrade last.
Running the same command in a Windows Command Prompt does work:
So it appears to be an issue with the MSYS2 console & parsing classpath string. I have not attempted a clean install yet.
The text was updated successfully, but these errors were encountered: