[GRADLE-833] Implement easy way to add plugins to configurations Created: 23/Feb/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Peter Ledbrook | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
It would be useful to have a way of adding a plugin to a configuration. For example, I have a Grails plugin whose JAR I want to add to the host project's runtime classpath. It seems like an esoteric request, but there's definitely a reason for it. Ah, I remember now: it packages some classes that are used when running Grails in an embedded servlet container. The servlet container uses the runtime configuration, so I have to get the plugin JAR into that configuration somehow. Here's the original mailing list thread: http://old.nabble.com/Adding-plugin-as-runtime-dependency-to-project-td27637314.html Adam's suggested syntax is: dependencies {
runtime plugins[myplugin].classpath
}
|
| 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 Benjamin Muschko [ 10/Feb/17 ] |
|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |