Closed smgeorge99 closed 10 years ago
I've just posted a bug report for this issue to the gradle dev list, and according to them, the problem is that the plugin uses the gradle internal API.
The steer seems to be that gradle plugins shouldn't use the internal api, as it's not backwards compatible.
This issue is duplicated by the more general #44
Agreed. Closing in favor of #44.
My project has been using this plugin since we were on gradle 1.5. Our project has since upgraded to gradle 1.6, and it works fine there as well. However, when I tried to run it against gradle 1.7-rc-2, I get the following exception: