Tomas Aschan

That seems to have just set it back to start over again. Not sure how much detail I can share about the repo structure and contents (there's a lot of...

Hi again! Sorry for the silence here - I had to put this aside for a bit and focus on other stuff... I have since done two things: * enable...

I have stuff like this in the Java language server logs: ``` [Error - 1:46:53 PM] Dec 12, 2024, 1:46:45 PM FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: com.salesforce.bazel.eclipse.jdtls [104]...

Another example error: ``` [Error - 3:24:20 PM] Dec 12, 2024, 3:24:20 PM FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: com.salesforce.bazel.eclipse.jdtls [104] Unresolved requirement: Require-Bundle: com.salesforce.bazel.eclipse.core -> Bundle-SymbolicName: com.salesforce.bazel.eclipse.core; bundle-version="2.0.0.v20241211-1121";...

With the version I had this morning, `1.24.112141547`, a new log from just opening the project today ``` Dec 16, 2024 9:11:06 AM org.apache.aries.spifly.BaseActivator log INFO: Registered provider ch.qos.logback.classic.servlet.LogbackServletContainerInitializer of...

I have no idea what changed from before, but now it seems to work for me! Plugin loads reasonably fast, resolves external dependencies etc, and I get proper intellisense and...

I _think_ this might be what currently blocks builds on a bunch of PRs; if I do this locally (including adding the submodules) the tests that fail on those PRs...

I though the whole point of go.work was to enable rewrites and similar tweaks in development while explicitly not affecting usage when importing the module. Maybe worth verifying, but unless...