-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow custom java path #40
Comments
Which version of Java do you have? 17 or newer should work, although I am seeing cases where it crashes even with 17 There is a setting called "Nextflow > Java > Home" which allows you to set the equivalent of |
As I said, the system version is very old:
Sorry, you're totally right, I somehow missed this! Once I set it in the settings, everything started working: {
"nextflow.java.home": "/path/to/openjdk/22.0.2"
} |
Noting this in case others stumble across it: in case you use nextflow and java from a conda environment, set |
On our HPC the extension crashes with the following error. Full trace is below.
I had a look through the extension settings, but there isn't anything for specifying the Java path for the extension. HPC systems such as ours often have old system libraries but newer versions in modules, so it would be great to be able to vscode where to find a newer JDK.
This probably relates to but isn't the same as #35.
System Details:
Full traceback:
The text was updated successfully, but these errors were encountered: