Java runtime could not be located

[bsaby]

OS: win10
VScode: 1.17.2()x64/x86
Jdk: 1.8.0_151(x64/x86)
Plugin: daily build 59

Repro steps:

1. Install Language Support for Java by Ret hat and Java debug plugin
2. Reload
3. Open a project folder and open a .java file in this project

@yaohaizh

[yaohaizh]

@bsaby Is the JAVA_HOME set in your system environment?

[bsaby]

Yes. And after this error occured, restart vscode, Java runtime will work fine.

[yaohaizh]

It seems the value is not properly resolved by VSCode java extension at the first time. You need restart the VSCode after your set the system variable.

[akaroml]

@bsaby please verify if you can still reproduce the issue by setting JAVA_HOME properly.

[bsaby]

Still reproduce this issue by setting JAVA_HOME properly using daily build 60.
And this issue only reproduce when reload not restart vscode after installing two java plugin

[akaroml]

@yaohaizh please further investigate this issue.

[yaohaizh]

VSCode will not populate its system environment when reload. See the VSCode issue here: microsoft/vscode#6333

For what it's worth, as of 05 March, 2018 the problem illustrated in the original poster's screenshot still exists.

For Linux Mint 32-bit. Visual Studio code 1.20.1.

1. Installed /java/jdk1.8.0_161 in /usr directory. In /bin used java -version to verify that the Java executable could be run without error.

2. Added path to JDK in both user and workspace settings:

User Settings:

{
   "java.home": "/usr/java/jdk1.8.0_161",
}

Workspace Settings:

{
  "java.home": "/usr/java/jdk1.8.0_161",
  "python.pydev.java.home": "/usr/java/jdk1.8.0_161",
  "python.linting.pylintPath": "/usr/local/bin/pylint",
  "python.pythonPath": "/usr/bin/python3.5",
}

3. Although I'm creating Python 3.5 code and not Java code, installed the following extensions in response to guidance offered on this and other forums:

   

See also https://stackoverflow.com/questions/46751168/visual-studio-code-cant-find-jdk8

4. Although I have resolved other issues (such as the inabiity of Visual Studio Code to find the system's instance of pylint, the JDK problem persists. And as others with this problem have noted, the solutions offered aren't working.