Add more tips to Troubleshooting doc #98
Conversation
Signed-off-by: Michael Vorburger <mike@vorburger.ch>
|
Is there a way to increase logging verbosity which we could document here? Where does it actually log when it launches Bazel do to the queries to configure the classpath? That's not in the I know the Terminal has 2 tabs for Bazel Build Status and Java Build Status - let me amend to add a note to look at that... |
|
@vorburger I noticed the missing logging too. I suspect something is not ok with JDTLS SLF4J & Logback setup. I am investigating. Probably worth moving this into a separate topic. |
docs/troubleshoot.md
Outdated
| @@ -40,6 +40,8 @@ see [issue #94](https://github.com/salesforce/bazel-vscode-java/issues/94). | |||
| 1. Close (all of) your VSC windows | |||
| 1. `killall java` (check that `jps` only shows _Jps_ itself) | |||
| 1. `cd YOURPROJECT` | |||
| 1. `rm -rf bazel-*` removes all Bazel related temporary files of course; but this should almost never be required! | |||
| 1. `rm -rf .eclipse/` removes all files configuring this extension, this normally also isn't required, but just in case | |||
There was a problem hiding this comment.
I think that's too brute force. That's usually never needed. However, occasionally reset of JDTLS via Cmd+Shift+p and then Java: Clean Java Language Server Workspace.
There was a problem hiding this comment.
Yeah, agreed; sorry, I went a bit crazy there... 😸 I've removed this again now. See what's left?
==> #100 (yay, 💯 🚀 ) |
Signed-off-by: Gunnar Wagenknecht <gunnar@wagenknecht.org>
I just had it "not work" again...
... and this is a bunch of things I tried.
No cleaning helped, and then I did an update of the extension (thus the uninstall/reinstall tip), and it worked again.
Which seems very weird, given that there don't seem to be any major changes recently.
The menus were there, the extension was "activated" according to VSC, but it just didn't configure the project.
@guw