Android Studio: "Use default gradle wrapper" vs. "Use customizable gradle wrapper"

ZenBalance picture ZenBalance · Jul 17, 2014 · Viewed 42.2k times · Source

What exactly is the difference between Android Studio's Gradle options:

Android Studio->Preferences->Gradle

Use default gradle wrapper (recommended) and Use customizable gradle wrapper?

Background:

I am working on an Android project in Android Studio and using a Gradle wrapper.

However, when I use the Android Studio settings "Use customizable gradlew wrapper" every time my team members sync the Android Studio project using the gui command:

enter image description here

they find the gradle/wrapper/gradle-wrapper.properties date being updated (and resulting in a extra diffs on the git repo).

Switching to "Use default gradle wrapper" seems to solve this issue.

Answer

ChrLipp picture ChrLipp · Nov 25, 2014

See the IntelliJ IDEA help here:

  • Using the default gradle wrapper means that Gradle controls the version number
  • Using the customizable gradle wrapper means that IDEA controls the version number of the gradle wrapper.

The version number is stored in gradle/wrapper/gradle-wrapper.properties. So when you choose "using the customizable gradle wrapper" each time you are opening the project with IDEA, it will change the property file to adjust the wrapper version you specified in the IDEA project.

For the sake of repeatable builds (even on your continuous build server which doesn't run IDEA) let Gradle control the version number and use the default gradle wrapper.

You can set the version number which is used by Gradle inside your build.gradle with

// needs at least Gradle V1.7
wrapper {
    gradleVersion = '2.2.1'
}

or

// works with every Gradle version
task wrapper(type: Wrapper) {
    gradleVersion = '2.2.1'
}

Remark: don't forget that this configuration is only used for the generation of the wrapper. To activate it, you have to execute the generation with gradlew wrapper. This tasks updates the gradle-wrapper.properties which is used afterwards for all wrapper executions.