GraalVM not supported when the JDK is installed from Nix

[ThomasVitale]

I use Nix to manage my JDKs. Whenever I use Temurin, Zulu, or OpenJDK, the "Language Support for Java(TM) by Red Hat" extension can correctly use the Java version installed in a specific Nix development environment.

However, when I use GraalVM CE, the extension throws an error like the following:

I have created a repo with a minimal setup and detailed instructions to reproduce the error (issue number 1 in the README).

https://github.com/ThomasVitale/vscode-java-nix-issue

[wenytang-ms]

@ThomasVitale I can repro such issue.
That's because the Java installed via Nix is missing the release file under the JAVA_HOME path. If you add that release file, the error message will no longer appear.

I also check with the GraalVM that the latest jdk 24 contians the release file. so You need to update your Nix image.

cc @rgrunber @testforstephen

[ThomasVitale]

@wenytang-ms thanks so much for looking into this! I have raised the issue with the nixpkgs repository: NixOS/nixpkgs#435799

[rgrunber]

@wenytang-ms Even if the release file is not in place, we determine the version at https://github.com/Eskibear/node-jdk-utils/blob/12677bb28170dcff72a3af0c8cb46f609abdabb5/src/index.ts#L358-L389 . Does the cli-check (java -version) also fail due to the same issue ? Update: Nevermind, it looks like this is happening on the server-side. So it's a different validation. Happens at https://github.com/eclipse-jdt/eclipse.jdt.debug/blob/92c97501780b050c24415b79fb7928c5be3a4ab1/org.eclipse.jdt.launching/launching/org/eclipse/jdt/internal/launching/StandardVMType.java#L864-L868 , which is part of the validation.

[tsmaeder]

Thinking about the root cause here: the Eclipse-side VM launcher needs certain info to create a command line like where the system libraries are located. That's why we are using StandardVMType.validate to make sure the IVMInstall will be able to furnish info like the Java version, etc.
This works well when you have a rich configuration UI like we have in the Eclipse IDE. But in VS Code, configuration comes mostly from text files. In this context, would it make sense to implement a VM type and VM Install that just takes all information from configuration without a detection step? It would allow to service any format of VM Install. (We could call it the TrustMeBroVMType ;-))