[JIRA] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew

[fcamb...@java.net (JIRA)]

Frédéric Camblor updated JENKINS-15406 When using gradlew, root build script field is not used to locate gradlew Change By: Frédéric Camblor (04/Oct/12 4:26 PM) Description: 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 : {code} $ \ {WORKSPACE \ }/foo/gradlew  {code}  But for now, it is some sort of : {code} $ \ {WORKSPACE \ }/gradlew -p $ \ {WORKSPACE \ }/foo {code} 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

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira