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
[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)
found out that it was because there was already some .project file. (whcih i already deleted withotu keeping them of course sigh)
it would be nice to have an improved errro message in case there is a .project exisitng but the project cannot be loaded.
The error message is not clear for this problem and it took us almost few months before we could find this issue on github.
apupier
changed the title
"IllegalArgumentException: Path must include project and resource name" for some folders
"IllegalArgumentException: Path must include project and resource name" when unloadable .project file is present
May 2, 2022
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:
Environment
Steps To Reproduce
--> 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 agoseems not, i tried with VS Code 1.42.1 and extension 0.55.1 and there was already the issue.The text was updated successfully, but these errors were encountered: