Fred Bricon
Fred Bricon
@rajinder-yadav your screenshot is not showing local classes 1st. But if you think this is no longer an issue, I'll close this one.
Have you looked at the [codespaces+java documentation](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/setting-up-your-java-project-for-codespaces)? @testforstephen or @jdneo might be more familiar with running on codespace
I've tried https://github.com/microsoft/vscode-remote-try-java and while it runs fine on codespaces, It failed to run as a devcontainer locally, with a similar issue as @FRC9289's (failing to use the `java.jdt.ls.java.home` value...
The upstream fix has been included in vscode-java a while ago. Inlay hints no longer cause this issue.
So what happens with multiple tabs on the same in Che workspace, when that PR is applied?
> Che 7 will receive an error message. Can you provide a screenshot? I'm curious to see that. @tsmaeder is it possible for several people to work on the same...
Can you provide more details? like your project setup? maybe share your project?
So I'm assuming it's an Android project then? If so, then sorry but it's not supported by [vscode-java ](https://github.com/redhat-developer/vscode-java/issues/10#issuecomment-268834749)
Android uses special Gradle plugins to compute the project classpath, that are not supported in Buildship, the underlying Gradle Integration plugin we delegate Gradle support to.
This seems to have been fixed in jdt.core at some point. Latest vscode-java version shows no problem.