[GRADLE-2136] Third-party plugins cannot be applied by ID from external build scripts Created: 03/Mar/12  Updated: 26/Jan/17  Resolved: 26/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Duplicate Votes: 4


 Description   

I'm not sure if this is a known problem, but I wasn't able to find it. Anyway, the problem is that when you 'include' (apply) a script which uses an external plugin, then you can't refer to it by its name.

An example can be seen at [1]http://code.google.com/p/rivoli/sourc... - in line 29, we'd like to refer to the Clover plugin by its ID instead of by its class name.
----------------------------------------------------------------------------------------
[1] http://code.google.com/p/rivoli/source/browse/gradle/sub/coverage.gradle

 Comments   
Comment by Justin Ryan [ 05/Apr/12 ]

I've seen this not work:

  1. build.gradle has "apply from: file('license.gradle')"
  2. license.gradle has "apply plugin: 'license'

But this does work:

  1. build.gradle has "apply from: file('license.gradle')"
  2. license.gradle has "apply plugin: nl.javadude.gradle.plugins.license.LicensePlugin
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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Micah Zoltu [ 20/Nov/16 ]

I believe this request has the requisite contents. It is a pretty simple request, and last I heard an issue that was being investigated by the Gradle dev team. I think this should be migrated to GitHub, though unclear whether it is a feature request or a bug report.

Comment by Benjamin Muschko [ 26/Jan/17 ]

The issue is now tracked on GitHub: https://github.com/gradle/gradle/issues/1262

Generated at Wed Jun 30 12:13:46 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.