Michael Vorburger

> haven't tried https://github.com/georgewfraser/java-language-server out I meanwhile did, and ran into [some problems](https://github.com/georgewfraser/java-language-server/issues?q=author%3Avorburger+). > Bazel-VSC-Java integration in your (unreleased) https://github.com/salesforce/bazel-vscode > a releasable state in the next few months ACK....

@guw I don't have the bandwidth to actively contribute with code (unfortunately; I would love to, this sounds, but I just don't have time for this; sorry), but https://github.com/salesforce/bazel-vscode-java/issues/49 has...

@guw just FYI (#111 is more important) when I press the Run | Debug on https://github.com/enola-dev/enola/blob/e6240391f16815c0b30e9c0ab10def17aff786e7/tools/hello/src/main/java/dev/enola/common/hello/Hello.java then the Terminal has: cd /home/vorburger/git/github.com/en ola-dev/enola ; /usr/bin/env /usr/lib/jvm/java-21-openjdk-21.0.2.0.13-1.fc39.x86_64/bin/java -agentlib:jdwp=transport=dt_socke t,server=n,suspend=y,address=localhost:33795 @/tmp/cp_5j8filafnox1ol2nueofo8mx9.argfile dev.enola.common.hello.Hello...

It seems to create a new `.vscode/launch.json` (which I didn't have before) which contains, among other things: ```json { "type": "java", "name": "Hello", "request": "launch", "mainClass": "dev.enola.common.hello.Hello", "projectName": "tools.hello:hello" }...

BTW: I was never entirely sure what _"for the Bazel Run Targets we rely on importing IJ run configurations"_ ([here](https://github.com/salesforce/bazel-vscode-java/issues/80#issuecomment-1879725172)) means... surely not that one needs to install IJ to...

@guw I do have [this](https://marketplace.visualstudio.com/items?itemName=redhat.java) (from MSFT) but not [this](https://marketplace.visualstudio.com/items?itemName=JavaTest.java-test&ssr=false#overview) (which looks old), and the [debugger](https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-debug). I do have that green double arrow in the side bar. Clicking it opens...

OMG 😮 I just discovered https://github.com/bazelbuild/bazel/issues/312 and was e.g. able to: $ b test --java_debug //common/common:src/test/java/dev/enola/common/io/resource/ResourceProvidersTest and then modify `"port": "5005"` in that `.vscode/launch.json` ([discovered here](https://github.com/salesforce/bazel-vscode-java/issues/80#issuecomment-2054218878)) and with that it...

I also seem to need to manually set e.g. `"projectName": "common.common:common"` to be able to see _Variables_ and _Watch._

> BTW: I was never entirely sure what "for the Bazel Run Targets we rely on importing IJ run configurations" (https://github.com/salesforce/bazel-vscode-java/issues/80#issuecomment-1879725172) means... surely not that one needs to install IJ...

I'm not sure if both jdt as well as eclipse are required.. I've only used jdt in the examples, and eclipse seems to be for plexus-compiler-eclipse, which ... is old?...