[GRADLE-2545] Wrong JAVA_HOME setting Created: 03/Nov/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-3 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Vadym | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
After installing I got error ERROR: JAVA_HOME is set to an invalid directory: /usr/lib/jvm/default-java Please set the JAVA_HOME variable in your environment to match the But I have correct JAVA_HOME. export JAVA_HOME=/usr/lib/jvm/default-java
I think it is something wrong with first line. |
Comments |
Comment by Adam Murdoch [ 04/Nov/12 ] |
There have been lots of fixes to the script since Gradle 1.0-milestone-3. Can you try a more recent version of Gradle and let us know if the problem still exists? |
Comment by pinaki [ 26/Dec/13 ] |
I have downloaded and extracted the gradle-1.9 and the java-1.7. The environment variable for java and gradle has been set too. But unfortunately me too getting the same error message. If needed more information please post it here. |
Comment by fabio [ 16/May/14 ] |
this error persists on ubuntu 14.04 x64. before editing: /usr/bin/gradle CLASSPATH=$APP_HOME/lib/gradle-launcher-1.4.jar
export JAVA_HOME=/usr/lib/jvm/default-java
after editing: /usr/bin/gradle CLASSPATH=$APP_HOME/lib/gradle-launcher-1.4.jar
# export JAVA_HOME=/usr/lib/jvm/default-java
Other informations: I'm not using OpenJDK7, but the Oracle-JDK7 installed as described in this link http://www.webupd8.org/2012/09/install-oracle-java-8-in-ubuntu-via-ppa.html dev@devworkstation:~$ gradle --version
------------------------------------------------------------
Gradle 1.4
------------------------------------------------------------
Gradle build time: Segunda-feira, 9 de Setembro de 2013 20h44min25s UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.3 compiled on April 8 2014
Ivy: non official version
JVM: 1.7.0_55 (Oracle Corporation 24.55-b03)
OS: Linux 3.13.0-24-generic amd64
|
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |