Sender | Message | Time |
---|---|---|
24 May 2024 | ||
spamegg1 | I have SDKMAN installed which lets me easily install and switch between many JVM versions. | 09:48:05 |
spamegg1 | https://sdkman.io/ | 09:48:14 |
spamegg1 | I think cs (Coursier) can also do it but I'm not sure. | 09:48:32 |
spamegg1 | * I think cs (Coursier) or scala-cli can also do it but I'm not sure. | 09:48:48 |
spamegg1 | Download Screenshot_from_2024-05-24_12-49-03.png | 09:49:25 |
spamegg1 | I have these JVMs installed | 09:49:26 |
spamegg1 | I set it to 17. Then I set the VS Code settings like in the screenshots above. | 09:49:51 |
spamegg1 | Anyway you should consider updating stuff in your project. Get the latest Sbt 1.10, update Scala to 2.13.14, update the dependencies, and so on. | 09:50:52 |
im_bharadwajj | ok thank you, i will go through it | 09:51:15 |
edmisml | Redacted or Malformed Event | 13:45:46 |
edmisml | Redacted or Malformed Event | 13:46:06 |
edmisml | Hi there, I'm trying to update to metals 1.21.1 on my work machine which uses ZScaler. Is there anyway to download the dependencies metals needs from the command line? In the past I've needed to install dependencies with courser doing something like this
to force it to use my default java that includes all necessary certs. | 14:13:59 |
edmisml | It seems I have installed Metals 1.2.1 now but it now reports build server is not "auto-connectable" | 14:31:59 |
edmisml | it seems as though a generate bsp-config command did the trick | 14:44:12 |
edmisml | apologies for blowing this thread up but it seems like Metals still reports 2024.05.24 10:11:03 WARN Build server is not auto-connectable. regardless if I use JDK 17 or 21. If I manually run the generate bsp-config command it appears to use sbt as the build server. I find this confusing as when I was using version 0.11.12 it was using bloop as the build server. | 15:12:56 |
edmisml | Note there is a build.sbt file present in the current working directory | 15:13:37 |
edmisml | If it's helpful the Run Doctor output is | 15:16:35 |
Tomasz Godzik | You should not need to run anything manually. Maybe best to reset the workspace and it should ask to auto import from sbt | 15:19:01 |
edmisml | by reset the workspace, do you mean something like "reload the window" | 15:19:13 |
Tomasz Godzik | there is a reset workspace command | 15:20:28 |
Tomasz Godzik | also available in the metals view | 15:20:33 |
Tomasz Godzik | or you can do it manually removing .metals .bloop and .bsp folders | 15:20:56 |
edmisml | Hrm I don't see this command | 15:23:46 |
edmisml | Deleted the .metals dir. There were not (and haven't been any automatically created) bsp or bloop directories | 15:26:30 |
Tomasz Godzik | if you reload the window does it suggest to import things? | 15:28:45 |
edmisml | it does not | 15:28:51 |
edmisml | what's strange is that when I switch the metals version to 0.11.12 and "import build" it "works". It creates the .bloop directory and everything compiles as expected | 15:30:17 |
edmisml | In 0.11.12 it seems to successfully connect to bloop 1.5.6 (reported by run doctor) | 15:32:44 |
edmisml | Is the VSCode extension known to work with Metals version 1.2.1? | 15:36:19 |
Tomasz Godzik | Yes, I mean I am using it 😅 | 15:55:02 |