Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

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.

like image 251
ZenBalance Avatar asked Jul 17 '14 19:07

ZenBalance


People also ask

What is default Gradle wrapper?

As per my knowledge, "default gradle" is the one that is packaged with the project. This is done so everyone in the team uses the same version. Local gradle is the one you have on your system.

Do I need Gradle wrapper?

you don't need to have Gradle installed on your machine to build the project. the wrapper guarantees you'll be using the version of Gradle required by the project. you can easily update the project to a newer version of Gradle, and push those changes to version control so other team members use the newer version.

Should I commit Gradle wrapper folder?

From Gradle's documentation:The scripts generated by this task are intended to be committed to your version control system. This task also generates a small gradle-wrapper. jar bootstrap JAR file and properties file which should also be committed to your VCS.

Why do we use Gradle wrapper?

Gradle is commonly used by developers to manage their project's build lifecycle. It's the default choice of build tool for all new Android projects. In this tutorial, we'll learn about Gradle Wrapper, an accompanying utility that makes it easier to distribute projects.


1 Answers

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.

like image 186
ChrLipp Avatar answered Sep 18 '22 19:09

ChrLipp