Missing IDE info

[ha1dfo]

I'm trying to set up bazel + java + vscode.

I have found this extension but having trouble setting it up.
Environment: build uses bazelmod and rules_jvm_external to fetch remote maven artifacts (they get put under .bazel/bin/**/*.jar.

I have created an empty WORKSPACE file (i know, it's fairly unnecessary if you use bazelmod, but i gave it a try).
It looks like my projects now do see each-other, but none of my external dependencies (maven) resolve.

When looking into "Problems" tab on vscode, I'm seeing these two things repeated over and over again:

• The project cannot be built until build path errors are resolved (I guess this is a result)
• Unable to compute classpath for target '//lib/java/<project>:<targetname>' because of missing IDE info! Please check the Bazel build for problems building the target. (Cause?)

On top of all this, my generated code (gRPC) doesn't seem to be picked up, but that might hopefully egt resolved automatically once I manage to address the above two issues.

I wonder if anyone would be able to help me figure out either/both of those issues? How to pick up external dependencies, and how to make the other error go away?

[guw]

Can you try with the latest build (preview release) published as:
https://marketplace.visualstudio.com/items?itemName=guw.bazel-eclipse-vscode

I don't know if the Salesforce extension is still published and maintained externally at this point.
https://github.com/eclipseguru/bazel-eclipse?tab=readme-ov-file#vs-code--cursor--theia-bazel-extension-for-vs-code

[ha1dfo]

I can confirm, WORKPACE file is no longer required (yay!)
However, the behavior is somewhat regressed: now the errors say:
Project 'lib.java.<component>:<target>' is missing required source folder: 'src/main/java'.
And the missing IDE info error is still present.

When opening Java: Configure Classpath, it doesn't have any sources root mentioned, when trying to add it manually it says The source path must be contained in the project root folder.

Also, the external maven dependencies are still missing.

Any pointers what changes I could make?

[guw]

Can you provide a sample setup of your workspace? It's hard to guess without understanding what kind of setup you use. Bazel is very flexible.

In principle we support two possible setups:
(1) Maven like and (BUILD file per module with glob for src/main/java/**/*.java)
(2) Bazel like (BUILD file in every Java package)

See: https://github.com/eclipseguru/bazel-eclipse/blob/main/docs/common/projectviews.md

[ha1dfo]

Here's a repro for how the repo looks like: https://github.com/ha1dfo/java-repro

As I was building this, I've noticed a lot more "wonkiness" in the system:

1. When opening this on a fresh laptop, java did find slf4j as maven dependency.
2. This made me suspect if there's something on my other setup that's causing it not to work. So removed all plugins and added necessary ones back. It took quite some aimless reloading, triggering no-op changes till java projects showed up. However, even after that, "Bazel Dependencies" seem empty for all.

Please advise what logs shall I collect.