[GRADLE-2407] Cannot load custom plugin (from outside distribution) to project from an init script Created: 30/Jul/12 Updated: 03/Feb/17 Resolved: 03/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Luke Daley | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 18 |
| Description |
|
At the moment, there's no way to apply a plugin (from outside of the Gradle distribution) from an init script. beforeLoad is too early as buildscript hasn't been evaluated. afterLoad works, but then the user cannot use any plugin features in their build script. |
| Comments |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Sebastian Schuberth [ 15/Nov/16 ] |
|
This still would be a useful feature in order to apply required plugins (e.g. as per company policy) for all current and future projects by simply adding them to the init script once. |
| Comment by Shami Willms [ 27/Dec/16 ] |
|
This would really help our company integrate with user's builds in Android Studio without requiring users to change their companies build script that is checked in. |
| Comment by Benjamin Muschko [ 03/Feb/17 ] |
|
The work is now tracked here: https://github.com/gradle/gradle/issues/1322 |