Gradle wrapper in a multi module project generates the wrapper for all modules instead of just once at the root


(Axel Fontaine) #1

gradle wrapper in a multi module project generates the wrapper for all modules instead of just once at the root

You then end up with one copy of the shell scripts and jars per module. Not good.


(Luke Daley) #2

Move the wrapper task out of the ‘allprojects {}’ or ‘subprojects {}’ block.


(Axel Fontaine) #3

I have neither.

I followed the instructions in the manual for the wrapper: http://www.gradle.org/docs/current/userguide/gradle_wrapper.html

And I added a settings.gradle for multiple modules, again following the manual: http://www.gradle.org/docs/current/userguide/multi_project_builds.html

Super basic build script, Gradle 1.6

Maybe the problem is in the docs?

But the real issue is: why do I even have to define the wrapper task? Can’t this be built in? This way errors like I just hit couldn’t even be possible (and the stupid copy paste of the wrapper snippet wouldn’t be needed either!)


(René Groeschke) #4

@Axel: In gradle 1.7 the wrapper tasks can be executed without the need of specifying it directly. More details about that can be found in the userguide of the latest nightly (http://www.gradle.org/docs/nightly/userguide/wrapper_plugin.html)


(Luke Daley) #5

Is this code somewhere I can take a look at?

The as documented way does work, so I think there’s something else at play here.