|
||||||||
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 |
[JIRA] (JENKINS-12769) Cannot specify location of gradle wrapper
david.pars...@gmail.com (JIRA) Thu, 10 Jan 2013 08:11:58 -0800
- [JIRA] (JENKINS-12769) Cannot specify l... spencer_all...@yahoo.com (JIRA)
- [JIRA] (JENKINS-12769) Cannot spec... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-12769) Cannot spec... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-12769) Cannot spec... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-12769) Cannot spec... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-12769) Cannot spec... david.pars...@gmail.com (JIRA)
What if the gradlew file does not reside in the root build script project? We're in the situation where we have a multi-project Gradle build, but we don't always want to build from the master directory (where gradlew resides).
I'd like the ability to supply a relative path to gradlew, or a relative folder where gradlew resides. That path should ideally be relative to the root build script directory.