Arthur McGibbon

@fiatjaf It works for me. If the semantic file isn't there then it hasn't compiled properly. Probably because it thinks that it's already compiled. You could try the Metals `Recompile...

@olafurpg has suggested [FileSystemProvider](https://code.visualstudio.com/api/references/vscode-api#FileSystemProvider) support which would allow proper exploration of the jars in the file explorer view (and bring back breadcrumbs) and seems fairly straightforward.

@tgodzik This is ready for review whenever you have time. I think the `FileWatcherLspSuite` test failure on the Mac is spurious as it happens on virtual docs and the readonly....

@tgodzik There is possibly a third way of implementing this. The LSP filesystem could present the exact file system info the jar has. e.g. `jar:file:///home/me/coursier/https/repo1.maven.org/maven2/org/scala-lang/scala-library/2.12.16/scala-library-2.12.16.jar` This would mean no special...

> There is possibly a third way of implementing this. > > The LSP filesystem could present the exact file system info the jar has. > e.g. jar:file:///home/me/coursier/https/repo1.maven.org/maven2/org/scala-lang/scala-library/2.12.16/scala-library-2.12.16.jar > Just...

@tgodzik > I am wondering though if we could do a proxy filesystem that would exactly the same mapping we do here and would work automatically with the new URIs....

I'm using JDK 17 and this won't compile for me because of various `bad path element` warnings and `-Werror` being set in the javac options. The `upgrade-system-tests-XX` projects have no...

@tgodzik thanks Reported https://github.com/scala/bug/issues/12594

Looking at this on my phone so it's a bit tricky. The way gradle works is that it always builds the jars for projects and sub projects. This appears to...

I can't examine the files locally but I imagine the reason bloop compiles is because you've already created the jar using gradle and that is what bloop is using. In...