Metals ignores JAVA_HOME because locate-java-home npm…

[hedefalk]

metals-vscode doesn't honor JAVA_HOME because it uses locate-java-home npm packages that doesn't. There's a PR to fix that but it seems to be a dead project?

There's a fork for this:
jvilk/locate-java-home#10 (comment)

https://github.com/viperproject/locate-java-home

Maybe metals can switch to that?

❯ npx locate-java-home                                                                                                                                           
npx: installed 4 in 1.996s
JAVA_HOME directories found: 

❯ echo $JAVA_HOME
env-/nix/store/7gxklxmf8d2c15jmw3i9l67kd2zci3w5-adoptopenjdk-hotspot-bin-11.0.10

✗ npx viperproject/locate-java-home 
npx: installed 5 in 26.395s
JAVA_HOME directories found: 
11.0.10 /nix/store/7gxklxmf8d2c15jmw3i9l67kd2zci3w5-adoptopenjdk-hotspot-bin-11.0.10 [64-bit] [JDK]
11.0.10 /nix/store/7gxklxmf8d2c15jmw3i9l67kd2zci3w5-adoptopenjdk-hotspot-bin-11.0.10/Contents/Home [64-bit] [JDK]

Currently, I have to go in to vscode settings over and over to set something dependent on my nix config.

Installation:

• Operating system: macOS

[tgodzik]

Thanks, the project indeed seems to be dead, I think it should be good to switch to that fork.

[tgodzik]

Is that fork released anywhere? @hedefalk ?I don't see anything here https://www.npmjs.com/search?q=locate-java-home%20

[hedefalk]

Ouch, I thought is was since I could run npx viperproject/locate-java-home but that pulls straight from github I guess.

[hedefalk]

@ArquintL Would it be possible to publish this on npm? See above ^

[dos65]

Additional thing, I have several jdk installed on Ubuntu.
The selected one is jdk 11(using update-alternatives) but extension ignores this facts and always picks jdk17.

[ArquintL]

@ArquintL Would it be possible to publish this on npm? See above ^

It is now available on NPM: @viperproject/locate-java-home