-
Notifications
You must be signed in to change notification settings - Fork 27
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
Support for JAVA_HOME env variable #25
Comments
techieBrandon
added a commit
to techieBrandon/grunt-sonar-runner
that referenced
this issue
Sep 14, 2016
techieBrandon
added a commit
to techieBrandon/grunt-sonar-runner
that referenced
this issue
Sep 14, 2016
techieBrandon
added a commit
to techieBrandon/grunt-sonar-runner
that referenced
this issue
Sep 14, 2016
techieBrandon
added a commit
to techieBrandon/grunt-sonar-runner
that referenced
this issue
Sep 14, 2016
skhatri
added a commit
that referenced
this issue
Oct 21, 2016
Issue #25: Adding capability to set JAVA_HOME for jvm in use
Fixed by 369cad2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a case where default installed java is 1.7 while SonarQube 5.6 requires JDK 1.8. For java builds we simply set the
JAVA_HOME
to point to the 1.8 version of JDK.Unfortunately this does not work for our javascript builds because
grunt-sonar-runner
does not take it into account when finding java to run (which java
is used).I think it would be nice if
grunt-server-runner
would pickjava
fromJAVA_HOME
if it is set.The text was updated successfully, but these errors were encountered: