search

Umoxfo / vscode-w3cvalidation

Adds W3C validation support to Visual Studio Code.
https://marketplace.visualstudio.com/items?itemName=Umoxfo.vscode-w3cvalidation
MIT License
9 stars 1 forks source link

constantly getting "java runtime could not be located" messages #19

Open mttindustries opened 4 years ago

mttindustries commented 4 years ago

I've been constantly getting this constantly getting "java runtime could not be located" messages evertime I load VSC. I've followed all the instructions in the plugin details page. I've installed the java development platform and i've pointed all my settings to the correct location C:\Program Files\Java\jdk-13.0.2

but it's still not working

Umoxfo commented 4 years ago

Sorry, I could not reproduce your issue.

Please reinstall the latest JDK and add ";C:\Program Files\Java\jdk-13.0.2\bin" to the environment variable PATH.

mttindustries commented 4 years ago

yeah I tried that. Reinstalled JDK, updated the environmental variable path to include the \bin directory on the end. Tried updating viscode settings to do the same. didn't work. Tried reinstalling the extension, didn't work. tried it without the /bin/ in settings... still doesn't work

Umoxfo commented 4 years ago

Please try to restart the VSCode in order to load reliably the changed environment variables.,,

mttindustries commented 4 years ago

yes i've done that too each step. I even installed and new installation of viscode, restarted the computer even and it still does it

ghost commented 4 years ago

Have the same problem... Stopped working today.

colvacdir commented 4 years ago

I'm also getting the error, but only on an earlier version of VSCode. The latest insider build doesn't show the error? They are both using the EXACT same path.

W3C Validation: 2.6.1 macOS: 10.12.6 Java: 1.8.0_241-b07 Path: /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/jre

VSCode: 1.41.1 Error: "Java runtime could not be located."

VSCode: 1.44.0-insider No Error

Umoxfo commented 4 years ago

Sorry for the inconvenience. It lacked testing in the macOS environment, so I set up GitHub Actions to test in a cross-platform environment.