Using Gradle wrapper (./gradlew.sh) with subprojects

Question

I have a multi-project build with several sub projects and I want to use the gradle wrapper.

What's the idiomatic way to do this?

Should I configure the wrapper in every subproject by adding the following code to build.gradle in the root?

allprojects {
    task wrapper(type: Wrapper) {
        gradleVersion = '2.2'
    }
}

But then, do I check all the gradlew.bat, gradlew.sh, gradle/wrapper/gradle-wrapper.jar, etc. files from all the subproject directories into version control?? That seems inefficient, but if I don't then how can I execute ./gradlew.sh in a sub project directory? What is the preferred way to use gradle wrapper in a subproject?

Do developers just use the gradle installed on the filesystem for this case?

The most important question is the first: what's the idiomatic way to do this?

Answer 1

You should just have the wrapper task outside of the allprojects block so you only have one gradlew.bat, gradlew.sh, and gradle/wrapper/gradle-wrapper.jar at the top level of your project structure.

You can run the ./gradlew tasks --all to verify the wrapper can see the subproject tasks

Or you can run the ./gradlew <subproject_name>:tasks command to view just one subproject's tasks.