You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I receive the error "The type [type] cannot be resolved. It is indirectly referenced from required .class files." for java.lang.Object, java.lang.String and any other imports that's not from my project.
I'm on Windows 10, I have both Java 11 and 8 installed and JAVA_HOME is set to Java/jdk-11.0.2
The JDT server launches without issues. I've tried with both Linter and Diagnostics, but result is the same.
I also tried using vscode-java and I can launch the project no problem, same in command line.
Here's my .classpath file, it points to Java 1.8, but I can still compile on vscode, and I don't know the notation for Java 11.
Same problem here. On ubuntu, in ide-java's settings the java home is set to "/usr/lib/jvm/java-8-openjdk-amd64" and I receive warnings like "The type java.lang.Object cannot be received".
Could not determine java version from '11.0.3'.
java.lang.IllegalArgumentException: Could not determine java version from '11.0.3'.
at org.gradle.api.JavaVersion.toVersion(JavaVersion.java:72)
at org.gradle.api.JavaVersion.current(JavaVersion.java:82)
I receive the error "The type [type] cannot be resolved. It is indirectly referenced from required .class files." for java.lang.Object, java.lang.String and any other imports that's not from my project.
I'm on Windows 10, I have both Java 11 and 8 installed and JAVA_HOME is set to Java/jdk-11.0.2
The JDT server launches without issues. I've tried with both Linter and Diagnostics, but result is the same.
I also tried using vscode-java and I can launch the project no problem, same in command line.
Here's my .classpath file, it points to Java 1.8, but I can still compile on vscode, and I don't know the notation for Java 11.
The text was updated successfully, but these errors were encountered: