Correct installation for metals

[peter-jerry-ye]

Hi, I'm using Metals with Helix editor with a sbt project that is mixed with Scala and Java files. I had

• coursier to install sbt and bloop and latest snapshot version of metals
• System package manager that installed javac / java / java source files

The lsp seems to work and can give diagnostic information for scala files, but I still have some problems.

• In the .metals/metals.log, there are huge amount of errors all similar to this one:

ERROR error processing file:///home/zihang/.cache/coursier/v1/https/repo1.maven.org/maven2/com/typesafe/config/1.4.2/config-1.4.2-sources.jarjava.nio.file.NoSuchFileException: /home/zihang/.cache/coursier/v1/https/repo1.maven.org/maven2/com/typesafe/config/1.4.2/config-1.4.2-sources.jar

• For the scala file, only the type signature of symbols are displayed, but not document content, nor does goto definition work for standard library.
• No type signature / autocompletion for Java files, but goto definition works.

So what else should I configure to make it work smoothly?

[tgodzik]

In the .metals/metals.log, there are huge amount of errors all similar to this one:

Source jars are supposed to be downloaded when running build import. Any idea why it wouldn't be present in the coursier cache?

For the scala file, only the type signature of symbols are displayed, but not document content, nor does goto definition work for standard library.

If the indexing fail, which seems to be the case here. We don't know where to find the definition or which scaladocs to present.

No type signature / autocompletion for Java files, but goto definition works.

It's currently not supported in Java files.

[tgodzik]

I assume that on VSCode we need to trigger "import build". But how does that work on a standalone editor? Is the "import build" a lsp command? If that's the case, I may need to wait for the next version of helix when they support lsp command.

It is, but this can also be done via request message, when the build definition changes. You can run this also manually in the console. Just check the build tool page for that.

Not a slightest hint. It seems all the *-source.jar are missing, but this may be related to the previous problem that "import build" is not ran?

most likely

[peter-jerry-ye]

Ok, I see, so it's manual installation section for sbt. I tried that and problem solved. Thank you very much for your help.

[ckipp01]

btw if you use the nightly version of helix you don't need to do the manual installation. Instead that version of helix has the :lsp-workspace-command which gives you all the workspace commands, one of them build build-import. Then you can just select it and get the import. Much nicer than needing to manually do anything.

[ckipp01]

Also in case you didn't know, we have a #helix-users channel on our scalameta discord. :) https://discord.gg/VxKvTSnF

[peter-jerry-ye]

btw if you use the nightly version of helix you don't need to do the manual installation

Yes I noticed that. It's just I'm not a fan of building everything myself.

Also in case you didn't know, we have a #helix-users channel on our scalameta discord.

That's nice. The future of helix+scala seems very bright. Thanks for the information.