Add a config variable to allow users to set the Java executable location (fixes issue #57) #273
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue #57.
This adds a new configuration variable called
javaHomeOverride
. This allows users to explicitly set JAVA_HOME if it is not present or if they wish to use a different Java installation. The Java executable is looked up at${javaHomeOverride}/bin/java
in this case.This also changes the default behavior to use
$JAVA_HOME/bin/java
as the Java executable to be consistent.If neither of
javaHomeOverride
or the JAVA_HOME environment variable are set then the extension attempts to launchjava
in PATH as before.I'm happy to adjust this as needed, feedback welcome.