Run CodeLens does not respect Bloop-configured JVM

[harpocrates]

In my project's Bloop config, I have:

        "platform": {
            "name": "jvm",
            "config": {
                "home": "C:\\Users\\Alec\\MyJdks\\jdk\\jdk-11.0.16.1+1",
                "options": [
                ]
            },
            "mainClass": [
            ],
            "resources": [
            ]
        },

However, when I click "run" in the CodeLens, I see that metals-vscode is using the version of Java that corresponds to JAVA_HOME instead.

Expected behavior

I'd expect the CodeLens to run the main method using the Java version configured in the corresponding Bloop projects JVM configuration (eg. as bloop run would do).

Installation:

• Operating system: reproduced on Windows, though likely platform independent
• VSCode version: 1.81.1
• VSCode extension version: 1.24.5
• Metals version: 1.0.0

[tgodzik]

Thanks for reporting! You should be able to change the metals.javaHome setting to get the proper Java version. We don't have currently a way to get the Java home from Bloop config (aside from parsing json, which I would rather avoid). In the future, that setting will be the project Java Home and Metals will just use its' own separate (sometimes) JVM . That project java home would be exported during import to bloop config. So it should be the same.

I will leave this issue open, since we might be able to figure out how to solve this better in the future.

[tgodzik]

Well, this seem to be actually quite easy to do and I totally forgot