My legacy (2.12.17) Scala code no longer compiles

[ghost]

Hello all,

I just got a Metals update (v1.24.0) in VSCode (Fedora Linux 38). My Scala code is quite old and my build.sbt contains

scalaVersion := "2.12.17"

which used to work fine. Now Metals/SBT seems to use the wrong compiler and library (scala-library-2.13.10.jar is displayed). My code no longer compiles and gives my 600+ errors.

Please help!

[tgodzik]

Nothing should have really changed as far as compilation is concerned, we haven't removed any support. Can you run the doctor command? Are you able to import the build again or clean compile? Anything in the Metals output? Any details would be helpful.

[ghost]

The project folder contains the workspace-file the sbt file. The sources are inside the same folder. So:

project/build.sbt
project/project.code-workspace
project/src/main/scala/nl/mycompany/folder1
project/src/main/scala/nl/mycompany/folder2
project/src/main/scala/nl/mycompany/folder3

I have to add folder1, folder2 and folder3 to the workspace becuase the SVN plugin will not pick op the three repos otherwise.

[ghost]

Is there any way to revert to the previous version? I am close to a deadline and can not afford to spend time on this.

[ghost]

Yes, this is where it breaks. If I make a completely new workspace and do NOT add the subfolders to the workspace things work fine. As soon as I add the subfolders Metals starts compiling with the wrong Scala version and thing are broken.
This used to work fine with the previous version. The added subfolder where displayed and compiled with the same setting as the containing projects build.sbt specifies.

Unfortunately I need the subfolders or my SVN plugin will not pickup on the repos.

[ghost]

Final note: the SVN plugin now supports picking up on the repos without adding them as folders in the workspace. Not as nice as it was but at least I have a working environment now.

Thanks for the help.

[tgodzik]

In the previous versions we would pick up only the first folder and I guess that would be the one with build.sbt. Since the other folders were inside the first one this must have been handled correctly by sheer luck and that use case not take into account on purpose at all.

We assume that workspace folders would be separate from each other and I am not entirely sure how to handle this situation 🤔
Maybe we should add a heuristic that melds the workspaces together? But this might be hard to achieve, but you can report it as a feature request.

For the future, you can always revert the extension version in the extension tab if you are having difficulties with the newer version.