-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java Projects contains (empty) Referenced Libraries instead of Bazel Maven JAR dependencies #103
Comments
@guw FYI at least on 1 of my computers (I'm not sure what's different on this one) I can reproduce this problem reliably, it's still there even after I
Here's the log.txt - but it's "boring"? |
@guw I'm facing this on one machine, which blocks me from working in a certain environment (but it works fine on another computer); here is some additional information from my machine where this always happens, the Java Build Status shows:
The Bazel Build Status shows:
Which ^^^ is clearly wrong (I think?)... would you perhaps like to add some additional logging for when it Or perhaps I could even contibute some minor logging enhancements, some day... where in the code would this be? I have a hunch that the "different environment" may have something to do with how Bazel / Bazelik is installed / found. |
For the record, |
Is the |
It's this one and the same on the computer where it works and the one where it does not.
For comparison, on the computer where it works it's:
the interesting part of all of this to compare to above is:
I have a hunch that you have asked about this because of Where in the code does it determine that Strategy? What could cause that to be null? |
Hm, I just noticed that on the computer where it works I'm on VSC 1.86.2, and on the one where it doesn't I'm still on the older 1.85.1, due to ... internal work related reasons. Let me try to double check if it reproduces with 1.86.2 on that computer... |
That doesn't seem to help. Another difference between these 2 computers that I just found is that on the one where it works, In fact, the Bazel Build Status is now even completely empty, not even showing Synchronization Summary at all, anymore. I cannot even get it to show that Synchronization Summary with the So it probably fails to launch Bazel? Could we enable (or add, in code) better logging around that? Where in the code does it do that? Do you want to use (my!) https://github.com/vorburger/ch.vorburger.exec for fully logging the exec? 🤣 PS: I doubt #88 is solved. But that doesn't really matter here - whether it's launch |
For what it's worth, in my #94 related experiments for enola-dev/enola#519 I've run into Why on that one other computer it doesn't even show that is still a mystery to me. |
Can you check the JDTLS log file? Cmd+Shift+P > Java: Open Java Language Server Log File |
Closing as #obsolete (it works great for me right now). |
After a Clean Java Language Server Workspace for #102,
when I open e.g.
common/common/src/main/java/dev/enola/common/io/resource/FileResource.java
,which is an example intentionally chosen because that
common/common
"module" (Bazel target) doesn't depend on others,then those
com.google.common.io
Guava imports don't resolve and are red.In the "Java Projects" view, there is an (empty) Referenced Libraries, instead of Bazel Maven JAR dependencies.
enola-dev/enola#431 couldn't be the root cause of this, could it? There is no error in the
.log
about it...Perhaps it would be useful to add some additional
catch
andlog
in the part of the code which sets that up?The text was updated successfully, but these errors were encountered: