Skip to content
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

VSCode Spring boot tools 1.30.0 error trying to find JVM #726

Closed
RohacRichard opened this issue Feb 2, 2022 · 5 comments
Closed

VSCode Spring boot tools 1.30.0 error trying to find JVM #726

RohacRichard opened this issue Feb 2, 2022 · 5 comments
Labels
for: vscode something that is specific for VSCode type: bug type: install-issue

Comments

@RohacRichard
Copy link

Describe the bug
This morning there was a new version of Spring boot tools installed to my VS code instance. I was unable to start any Spring projects from dashboard. I managed to resolve the problem by downgrading to previous version. Maybe there is problem with something on my side. Just throwing this out in case anybody else has this problem.

To Reproduce
Install Spring boot tools 1.30.0 and restart java workspace. Throws this error:
Screenshot 2022-02-02 134256

@BoykoAlex
Copy link
Contributor

BoykoAlex commented Feb 2, 2022

Looks like the issue is:

ChildProcess.execSync(javaExecutable + ' --list-modules', {windowsHide: true, encoding: 'utf8'});

command string doesn't like spaces in paths./ Need to wrap javaExecutable in double quotes.

The workaround would be to have Java somewhere under the path not having spaces :-/

@BoykoAlex
Copy link
Contributor

Feel free to remove java home setting value in your VSCode settings. New Java extension for vscode comes with embedded java. If your vscode is located under the path without space then everything should start working if you remove java home setting from VSCode settings.

@BoykoAlex
Copy link
Contributor

BoykoAlex commented Feb 2, 2022

Fixed with 1980919. Should be available in 1.31

@martinlippert
Copy link
Member

We are in the process of pushing out another update release to get this into the hands of our users quickly. Stay tuned.

@martinlippert
Copy link
Member

Update releases with a fix for this published on the VSCode marketplace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: vscode something that is specific for VSCode type: bug type: install-issue
Projects
None yet
Development

No branches or pull requests

3 participants