VSCode libraries different and missing

[nilskp]

My project is defined as Scala 3.7.4, but for some reason Mill is using 3.8.0-RC3. And my Jetty dependencies are not listed, which also means that I cannot click through into any Jetty classes, although the project compiles, and runs, as expected.

[nilskp]

Scalatra is also missing. If I show the dependency tree, I see that there are some potential incompatibilities, so I'm wondering if that's the cause?

[lefou]

I think what you see in Metals/Packages/Libraries view are all libraries used by some part of the build. Since build.mill files are also Scala files which you might want to edit with Metals support, you see the Scala Library 3.8.0-RC3. Your own modules use Scala 3.7.4, which is using the Scala Library 2.13.x. Why it is not visible (and also not the other libraries like scalatra) in this view I can't tell and recommend to ask in a Metals support channel.

[nilskp]

I'm guessing the Metals simply display what's coming from the build server, so then the question would come back here. I have multiple libraries that are now inaccessible from VSCode.

[lefou]

Without a minimal reproduce, it's hard to guess what the root cause is.

You might want enable Metals debugging: https://scalameta.org/metals/docs/integrations/debug-adapter-protocol#debugging-the-connection

Mill is also writing some trace files, e.g. .bsp/mill-bsp-out/mill-bsp/trace.log (since 1.1.0-RC3) or out/mill-bsp-out/mill-bsp/trace.log.