redhat-developer / redhat-developer/vscode-java
Update jdk and old workspace still points to the stale JRE system libraries
@snjeza ya está trabajando en esto.
Desde el 20/1/2018.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.3k
- Forks
- 546
- Merge medio
- 20 h 1 min
- PR fusionados (30 d)
- 11
Descripción
Steps to reproduce:
-
Install jdk1.8.0_131 in windows 10, and set JAVA_HOME and Path environment variables.
-
Install latest vscode-java extension in vscode, and open a java 8 maven project.
-
F12 at
java.io.PrintStream.println, jump to editorcontents/rt.jar/java.io/PrintStream.class. -
Install the latest jdk-9.0.1 and update JAVA_HOME and Path environment variables.
-
Restart vscode window.
-
F12 at
java.io.PrintStream.println, still jump to the stale jre sourcecontents/rt.jar/java.io/PrintStream.class. It's supposed to jump to the java 9 sourcecontents/java.base/java.io/PrintStream.class.
Actually the java language server was launched by the new java 9 jvm, but the workspace cached the old JRE 8 system libraries and user has no way to change the JRE system libraries.
Current workaround is to clean up the vscode local storage directory C:\Users\jinbwan\AppData\Roaming\Code - Insiders\User\workspaceStorage.
Expected:
When vscode-java extension startup, update the workspace jre container to the one under JAVA_HOME silently.
Or provide a command to allow user to update the workspace JRE container.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.