|
||||||||
|
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
spencer_all...@yahoo.com (JIRA) Mon, 26 Nov 2012 06:26:52 -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)
This is a current blocker for attempting to utilize this gradle plugin and the gradle wrapper together for several valid use cases. There were two highly generalized solutions that are in pull requests from about 3 months ago (there might be some reason why they were not incorporated, as I've not tested either). I submitted a limited solution just over a week ago as a pull request that simply allows gradlew to selectively be found in the same directory as the root build file or workspace top, which required very minor modifications to the existing code base.