redhat-developer / redhat-developer/vscode-java
"IllegalArgumentException: Path must include project and resource name" when unloadable .project file is present
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.3k
- Forks
- 546
- Merge medio
- 20 h 1 min
- PR fusionados (30 d)
- 11
Descripción
Java extension is not working when opening some folders (it works for soem others).
For instance when opening the folder examples of https://github.com/apache/camel-k/tree/master/examples
there is this error in output:
[Error - 3:33:47 PM] May 13, 2020 3:33:47 PM An internal error occurred during: "Initialize workspace".
Path must include project and resource name: /examples
java.lang.IllegalArgumentException: Path must include project and resource name: /examples
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:66)
at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2122)
at org.eclipse.core.internal.resources.Container.getFolder(Container.java:205)
at org.eclipse.jdt.ls.core.internal.managers.StandardProjectsManager.registerWatchers(StandardProjectsManager.java:311)
at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer$1.run(JDTLanguageServer.java:277)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Environment
- Operating System: Fedora 31
- JDK version: Java 8
- Visual Studio Code version: 1.45.0
- Java extension version: 0.61.0
Steps To Reproduce
- clone locally https://github.com/apache/camel-k/
- in VS Code, File -> Open Folder...
- select the examples folder inside the cloned repository
- Open one of the Java files
--> stack trace in output log
--> several errors reported in files
[Please attach a sample project reproducing the error]
full log with trace activated:
https://gist.github.com/apupier/ca016099587a7730745d1841b094f7e6
Current Result
Expected Result
Additional Informations
it was working few weeks/months ago seems not, i tried with VS Code 1.42.1 and extension 0.55.1 and there was already the issue.
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.
Línea de trabajo
Reproduce el fallo abriendo la carpeta de ejemplos de apache/camel-k en VS Code y revisa el registro completo enlazado. Comienza en StandardProjectsManager.java:311 y JDTLanguageServer.java:277 en el stack trace; se considera terminado cuando abrir la carpeta ya no produce IllegalArgumentException ni errores de archivo relacionados.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, vscode
- Área
- devtools
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100