JAVA_HOME is not pointing to a JDK.
See original GitHub issue[provide a description of the issue]
Environment
-
Operating System: macOS Mojave
-
JDK version: OpenJDK 11.4
-
Visual Studio Code version: 1.38.1
-
Java extension version: 0.48.0
Steps To Reproduce
- Opening Java Project
Current Result
After opening a Java project, the configure window pops up and shows, that the JAVA_HOME
is set, but it’s not pointing to a JDK.
The JAVA_HOME
path is correctly set.
Expected Result
JDK should be found.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:29 (7 by maintainers)
Top Results From Across the Web
Ant "JAVA_HOME does not point to the JDK" - but it does
Try the following command in a terminal: "%JAVA_HOME%\bin\javac". If the command does not exist that proves you don't have a JDK installed. –...
Read more >Maven Error “JAVA_HOME should point to a JDK not a JRE”
In this tutorial, we're going to talk about an exception that Maven throws when misconfigured: JAVA_HOME should point to a JDK, not a...
Read more >Installing the JDK Software and Setting JAVA_HOME
Procedure To Install the JDK Software and Set JAVA_HOME on a Windows System · Right click My Computer and select Properties. · On...
Read more >JAVA_HOME does not point to the JDK - Struts - CodeRanch
You have pointed JAVA_HOME at the JRE, not the JDK. You need to point it at wherever you installed the JDK. reply ·...
Read more >Troubleshooting on Windows - GitHub Pages
DAISY Pipeline 2 uses the Windows environment variable JAVA_HOME to find your Java installation folder. This error can occur if the variable is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same problem on my Mint. The problem was fixed after I reinstalled openjdk-11. I used the following command. Should work for Ubuntu as well.
sudo apt install openjdk-11-*
Got the same error on Linux Debian 10.5 (buster). I realized that if I was launching VSC by the application itself, it was doing this error, while if I launch VSC through the terminal, all’s good. Maybe user’s settings.