Gradle: Could not determine java version from '11.0.2'

Java Problem Overview

I ran the following comment:

./gradlew app:installDebug

only to be met with the log:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '11.0.2'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

My version of gradle is 5.1.1:

------------------------------------------------------------
Gradle 5.1.1
------------------------------------------------------------

Build time:   2019-01-10 23:05:02 UTC
Revision:     3c9abb645fb83932c44e8610642393ad62116807

Kotlin DSL:   1.1.1
Kotlin:       1.3.11
Groovy:       2.5.4
Ant:          Apache Ant(TM) version 1.9.13 compiled on July 10 2018
JVM:          11.0.2 (Oracle Corporation 11.0.2+9-LTS)
OS:           Mac OS X 10.13.6 x86_64

I'm not sure how to proceed (I tried upgrading/downgrading, but nothing has worked so far).

UPDATE: When I ran ./gradlew --version, I got the following:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '11.0.2'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

My .../gradle/wrapper/gradle-wrapper.properties contains the following including distributionUrl=.../gradle-4.1-rc-1-all.zip:

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-4.1-rc-1-all.zip

Java Solutions

Solution 1 - Java

There are two different Gradle applications in your system.

the system-wide Gradle
This application is invoked by gradle (arguments).
the gradle-wrapper
The gradle-wrapper is specific to every project and can only be invoked inside the project's directory, using the command ./gradlew (arguments).

Your system-wide gradle version is 5.1.1 (as the OP explained in the comments, running the command gradle --version returned version 5.1.1).

However, the failure is the result of a call to the gradle-wrapper (./gradlew). Could you check your project's gradle wrapper version? To do that, execute ./gradlew --version inside your project's folder, in the directory where the gradlew and gradlew.bat files are.

Update 1:
As running ./gradlew --version failed, you can manually check your wrapper's version by opening the file:

> (project's root folder)/gradle/wrapper/gradle-wrapper.properties

with a simple text editor. The "distributionUrl" inside should tell us what the wrapper's version is.

Update 2: As per the OP's updated question, the gradle-wrapper's version is 4.1RC1.
Gradle added support for JDK 11 in Gradle 5.0. Hence since 4.1RC does not support running on JDK 11 this is definitely a problem.

The obvious way, would be to update your project's gradle-wrapper to version 5.0.
However, before updating, try running gradle app:installDebug. This will use your system-wide installed Gradle whose version is 5.1.1 and supports running on Java 11. If this works, then your buildscript (file build.gradle) is not affected by any breaking changes between v.4.1RC1 and v.5.1.1 and you can then update your wrapper by executing from the command line inside your project's folder: gradle wrapper --gradle-version=5.1.1 [*].

If gradle app:installDebug fails to execute correctly, then maybe you need to upgrade your Gradle buildscript. For updating from v.4.1RC1 to 5.1.1, the Gradle project provides a guide (1, 2) with breaking changes and deprecated features between minor releases, so that you can update gradually to the latest version.

Alternatively, if for some reason you can't or don't want to upgrade your Gradle buildscript, you can always choose to downgrade your Java version to one that Gradle 4.1RC1 supports running on.

[*] As correctly pointed out in the answer by @lupchiazoem, use gradle wrapper --gradle-version=5.1.1 (and not ./gradlew as I had originally posted there by mistake). The reason is Gradle runs on Java. You can update your gradle-wrapper using any working Gradle distribution, either your system-wide installed Gradle or the gradle-wrapper itself. However, in this case your wrapper is not compatible with your installed Java version, so you do have to use the system-wide Gradle (aka gradle and not ./gradlew).

Solution 2 - Java

As distributionUrl is still pointing to older version, upgrade wrapper using:

gradle wrapper --gradle-version 5.1.1

Note: Use gradle and not gradlew

Solution 3 - Java

Updating gradle/wrapper/gradle-wrapper.properties with the following version fixed it for me:

distributionUrl=https\://services.gradle.org/distributions/gradle-5.4.1-all.zip

Solution 4 - Java

In my case the JAVA_HOME variable was set to /usr/lib/jvm/jdk-11.0.2/. It was sufficient to unset the variable like this:

$ export JAVA_HOME=

Solution 5 - Java

tl;dr: downgrade java by running update-alternatives

My system gradle version was 4.4.1, and the gradle wrapper version was 4.0. After running the command given by several other answers:

gradle wrapper --gradle-version 4.4.1

I still had the same error:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '11.0.4'.

It turns out java 11 wasn't supported until gradle 4.8, and my software repositories only had 4.4.1. (Also, upgrading to newer gradle version might have been incompatible with the package I was trying to compile.)

The answer was to downgrade java. My system actually had java8 already installed, and it was easy to switch between java versions by running this command and following the instructions:

sudo update-alternatives --config java

Solution 6 - Java

Because your wrapper version does not support 11+ you can make simple trick to cheat newer version of InteliJ forever.

  press3x Shift -> type "Switch Boot JDK" -> and change for java 8.

Or If you want to work with java 11+ you simply have to update wrapper version to 4.8+

Solution 7 - Java

I had the same problem here. In my case I need to use an old version of JDK and I'm using sdkmanager to manage the versions of JDK, so, I changed the version of the virtual machine to 1.8.

sdk use java 8.0.222.j9-adpt

After that, the app runs as expected here.

Solution 8 - Java

I've had the same issue. Upgrading to gradle 5.0 did the trick for me.

This link provides detailed steps on how install gradle 5.0

Solution 9 - Java

To put long answer short, upgrade your gradlew using the system gradle tool. Note that the below upgrade works even if your system gradle version is < 5.

gradle wrapper --gradle-version=5.1.1

Solution 10 - Java

In my case, I was trying to build and get APK for an old Unity 3D project (so that I can play the game in my Android phone). I was using the most recent Android Studio version, and all the SDK packages I could download via SDK Manager in Android Studio. SDK Packages was located in

C:/Users/Onat/AppData/Local/Android/Sdk

And the error message I got was the same except the JDK (Java Development Kit) version "jdk-12.0.2" . JDK was located in

C:\Program Files\Java\jdk-12.0.2

And Environment Variable in Windows was JAVA_HOME : C:\Program Files\Java\jdk-12.0.2

After 3 hours of research, I found out that Unity does not support JDK 10, as told here. My suggestion is:

Uninstall unwanted JDK if you have one installed already.
Head here
Login to/Open a Oracle account if not already logged in.
Download the older but functional JDK 8 for your computer set-up(32 bit/64 bit, Windows/Linux etc.)
Install the JDK. Remember the installation path.
If you are using Windows, Open Environment Variables and change Java Path via Right click My Computer/This PC>Properties>Advanced System Settings>Environment Variables>New>Variable Name: JAVA_HOME>Variable Value: [YOUR JDK Path, Mine was "C:\Program Files\Java\jdk1.8.0_221"]
In Unity 3D, press Edit > Preferences > External Tools and fill in the JDK path (Mine was "C:\Program Files\Java\jdk1.8.0_221").
Also, in the same pop-up, edit SDK Path. (Get it from Android Studio > SDK Manager > Android SDK > Android SDK Location.)
If needed, restart your computer for changes to take effect.

Solution 11 - Java

I had a similar problem: my default gradle wrapper was version 4.x, while the support for higher versions of Java has been added in Gradle 5.

I've updated my gradlew as described here: https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:upgrading_wrapper

TLTD:

./gradlew wrapper --gradle-version 5.6.2

Solution 12 - Java

I have the similar issue in Windows with redhat java-11 version, edited the gradle-wrapper.properties and updated the distributionUrl as below with gradle-6.5.1-bin.zip and its working for me.

distributionUrl=https\://services.gradle.org/distributions/gradle-6.5.1-bin.zip

Solution 13 - Java

I had the same issue in Windows. My gradle configuration was to set use JDK1.8, but JAVA_HOME was configured to use another JDK.

Solution :

Set JAVA_HOME properly based on your configured JDK in gradle

Solution 14 - Java

If you've android studio version 4.2.2 its starts as default Java 11.0.8

Check your version Android Studio -> About Android Studio

Change 11.0.8 to JDK 8

1- Install the JDK8

2- Install the Choose Runtime plugin

3- Open action tab: Command + Shift + A ⇧⌘A

4- Choose runtime and select jdk 8 on list

Solution 15 - Java

Navigate to Project/gradle/wrapper/gradle-wrapper.properties and manually changed the distributionUrl to distributionUrl=https\://services.gradle.org/distributions/gradle-5.1.1-bin.zip and it worked Hope this helps someone.

Solution 16 - Java

Just goto your "project folder/gradle/gradle-wrapper.properties" and in distibutionUrl where your gradle version is metioned, check the new updated gradle version from here and change it in "distributionUrl" and done!

Solution 17 - Java

I solved this by clicking on File -> Project Structure then changed the JDK Location to Use Embedded JDK (Recommended)

Solution 18 - Java

Getting this error when doing a `cordova build android --release`

I was able to resolve this, after trying so so many different things, by simply doing :

npm install cordova -g   # to upgrade to version 10.0.0

cordova platform rm android
cordova platform add android    # to upgrade to android version 9.0.0

Solution 19 - Java

Head over toandroid/gradle/wrapper/gradle-wrapper.properties and update the distributionUrl with the latest gradle version.

Go to https://gradle.org/releases/ to get the latest version, then edit it here.

> https\://services.gradle.org/distributions/gradle-7.3.3-all.zip

7.3.3 being the latest version release.

> https\://services.gradle.org/distributions/gradle-#latest_gradle-version#-all.zip

Solution 20 - Java

I ran into a similar issue. I deleted these:

libraries and caches from the .idea folder ( YourApp > .idea > .. ) AND
contents of the build folder.

then rebuild.

*** DON'T FORGET TO BACKUP YOUR PROJECT FIRST ***

Solution 21 - Java

I ran into the same issue in Ubuntu 18.04.3 LTS. In my case, apt installed gradle version 4.4.1. The already-install java version was 11.0.4

The build message I got was

Could not determine java version from '11.0.4'.

At the time, most of the online docs referenced gradle version 5.6, so I did the following:

sudo add-apt-repository ppa:cwchien/gradle
sudo apt update
sudo apt upgrade gradle

Then I repeated the project initialiation (using gradle init with the defaults). After that, ./gradlew build worked correctly.

I later read a comment regarding a change in format of the output from java --version that caused gradle to break, which was fixed in a later version of gradle.

Solution 22 - Java

got to project file.. gradle/wrapper/gradlewrapper.properties

there you can change the value of distributionurl to what ever the lastest version is. (Found on docs.gradle.org)

Solution 23 - Java

I was facing the same issue in Docker setup, while I was trying to install Gradle-2.4 with JDL 11.0.7. I have to install a later version to fix the issue.

Here is the Working Dockerfile

FROM openjdk:11.0.7-jdk
RUN apt-get update && apt-get install -y unzip
WORKDIR /gradle
RUN curl -L https://services.gradle.org/distributions/gradle-6.5.1-bin.zip -o gradle-6.5.1-bin.zip
RUN unzip gradle-6.5.1-bin.zip
ENV GRADLE_HOME=/gradle/gradle-6.5.1
ENV PATH=$PATH:$GRADLE_HOME/bin
RUN gradle --version

Solution 24 - Java

The simplest for a quick and dirty test is to just use an override, for example:

> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/ ./gradlew build

since the wrapper checks for JAVA_HOME you can just pick any you want on each run.

Solution 25 - Java

You might missed to install maven please install the maven then please checked. it will work after ....

Solution 26 - Java

As others have mentioned, Java 11 support was added in Gradle 5. The solution is to upgrade your Gradle wrapper:

Go here to figure out the latest version of Gradle: https://gradle.org/releases/
Upgrade the Gradle wrapper
- If you have Gradle installed on your machine:
```
gradle wrapper --gradle-version 7.2
```
- If you don't have Gradle installed:
  1. Modify gradle/wrapper/gradle-wrapper.properties
    
    Update distributionUrl with the latest version of Gradle, e.g.
```
distributionUrl=https\://services.gradle.org/distributions/gradle-7.2-bin.zip
```
  2. Upgrade the remaining wrapper files (gradle-wrapper.jar, gradlew, gradlew.bat)
```
./gradlew wrapper --gradle-version 7.2
```

Since you're upgrading from an old version of Gradle, you'll probably get errors like these:

Could not find method compile() for arguments ...
Could not find method testCompile() for arguments ...

To fix these, edit build.gradle and replace every instance of compile with implementation and replace testCompile with testImplementation.

Content Type	Original Author	Original Content on Stackoverflow
Question	lesley2958	View Question on Stackoverflow
Solution 1 - Java	tryman	View Answer on Stackoverflow
Solution 2 - Java	lupchiazoem	View Answer on Stackoverflow
Solution 3 - Java	Manuel Schmitzberger	View Answer on Stackoverflow
Solution 4 - Java	dr0i	View Answer on Stackoverflow
Solution 5 - Java	craq	View Answer on Stackoverflow
Solution 6 - Java	SuperAndrew	View Answer on Stackoverflow
Solution 7 - Java	Maciel Escudero Bombonato	View Answer on Stackoverflow
Solution 8 - Java	juancho85	View Answer on Stackoverflow
Solution 9 - Java	Rocky Inde	View Answer on Stackoverflow
Solution 10 - Java	Onat Korucu	View Answer on Stackoverflow
Solution 11 - Java	Nestor Milyaev	View Answer on Stackoverflow
Solution 12 - Java	Rajesh Boddepalli	View Answer on Stackoverflow
Solution 13 - Java	Jafar Karuthedath	View Answer on Stackoverflow
Solution 14 - Java	Ali Ozkara	View Answer on Stackoverflow
Solution 15 - Java	Denver Shenal	View Answer on Stackoverflow
Solution 16 - Java	Ankit Gupta	View Answer on Stackoverflow
Solution 17 - Java	Derrick Lamptey	View Answer on Stackoverflow
Solution 18 - Java	kris	View Answer on Stackoverflow
Solution 19 - Java	dev.bojack	View Answer on Stackoverflow
Solution 20 - Java	KHAN	View Answer on Stackoverflow
Solution 21 - Java	MgFrobozz	View Answer on Stackoverflow
Solution 22 - Java	atreyHazelHispanic	View Answer on Stackoverflow
Solution 23 - Java	Adiii	View Answer on Stackoverflow
Solution 24 - Java	juancn	View Answer on Stackoverflow
Solution 25 - Java	user14392109	View Answer on Stackoverflow
Solution 26 - Java	bmaupin	View Answer on Stackoverflow

Gradle: Could not determine java version from '11.0.2'

Java Problem Overview

Java Solutions

Solution 1 - Java

Solution 2 - Java

Solution 3 - Java

Solution 4 - Java

Solution 5 - Java

Solution 6 - Java

Solution 7 - Java

Solution 8 - Java

Solution 9 - Java

Solution 10 - Java

Solution 11 - Java

Solution 12 - Java

Solution 13 - Java

Solution 14 - Java

Solution 15 - Java

Solution 16 - Java

Solution 17 - Java

Solution 18 - Java

Getting this error when doing a `cordova build android --release`

Solution 19 - Java

Solution 20 - Java

Solution 21 - Java

Solution 22 - Java

Solution 23 - Java

Solution 24 - Java

Solution 25 - Java

Solution 26 - Java

Angular CLI Error: The serve command requires to be run in an Angular project, but a project definition could not be found

React.useState does not reload state from props

Attributions

Java Problem Overview

Java Solutions

Solution 1 - Java

Solution 2 - Java

Solution 3 - Java

Solution 4 - Java

Solution 5 - Java

Solution 6 - Java

Solution 7 - Java

Solution 8 - Java

Solution 9 - Java

Solution 10 - Java

Solution 11 - Java

Solution 12 - Java

Solution 13 - Java

Solution 14 - Java

Solution 15 - Java

Solution 16 - Java

Solution 17 - Java

Solution 18 - Java

Getting this error when doing a cordova build android --release

Solution 19 - Java

Solution 20 - Java

Solution 21 - Java

Solution 22 - Java

Solution 23 - Java

Solution 24 - Java

Solution 25 - Java

Solution 26 - Java

Angular CLI Error: The serve command requires to be run in an Angular project, but a project definition could not be found

React.useState does not reload state from props

Attributions

Getting this error when doing a `cordova build android --release`