|
|
_0.png) |
|
|
|
|
Issue Type:
|
 Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
gradle |
|
Created:
|
02/Jul/12 9:01 AM
|
|
Description:
|
The gradle Wrapper task creates the gradle wrapper scripts, but it does so in the project root, which sometimes is not wanted. One can override it, so that the scripts are found in, say, a 'contrib' folder, along with other helper scripts.
Jenkins Gradle plugin has the option to use the wrapper, but it blindly tries to invoke gradlew from the project root - it is unaware of custom settings.
Please let users define a custom path to the gradlew script within the project, or, ideally, read if somehow from the build.gradle file (it might be difficult, I aggree). Having users specify it explicitly is good enough, IMHO.
|
|
Environment:
|
all
|
|
Project:
|
Jenkins
|
|
Priority:
|
 Major
|
|
Reporter:
|
wujek srujek
|
|
|
|
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
|
|
Locked
I think a new textbox which allows to specify the gradle wrapper batch file parent would be the best solution. I would like to contribute a patch for that if there is no objection with this approach.