It seems "root build script" is not really well taken when using gradlew.

For instance, I have a git repository having a foo/build.gradle script.
I then set "root build script" to "${WORKSPACE}/foo/"

I would like to execute :

$\{WORKSPACE\}/foo/gradlew 

But for now, it is some sort of :

$\{WORKSPACE\}/gradlew -p $\{WORKSPACE\}/foo

I think we should define gradlew location (relative to checked out root repository) because for the moment, the only way to workaround the problem is to put gradlew in the root scm hierarchy