| Symptom | Resolution |
|---|---|
Nothing happens after opening a .java file |
Confirm the project is a Gradle, Maven, or Bazel project with a build file at or above the opened folder. If VS Code opened the folder in Restricted Mode, see Opened a Java project in VS Code but nothing happens: Restricted Mode blocks the extension. |
| Code is fully red, symbols unresolved | Allow import and indexing to finish. If it persists, run Reload Workspace, then Clear Caches and Restart Language Server. Verify intellij.jdkForSymbolResolution. |
| The wrong build tool is used for import | Set intellij.buildTool to gradle or maven. |
| A multi-build workspace is not imported correctly | Declare each build with intellij.projects. |
| A Bazel project is not imported as expected | Set intellij.bazel.projectview to the .bazelproject file. |
| Slow performance or out-of-memory on a large project | Increase the heap through intellij.additionalJvmArgs, for example ["-Xmx4g"]. |
To collect logs, set intellij.trace.server to verbose or messages. The trace appears in the extension's Output channel.
Comments
0 comments
Please sign in to leave a comment.