[GRADLE-1517] Apply statement not using script classpath Created: 08/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Marco Hunsicker Assignee: Unassigned
Resolution: Won't Fix Votes: 11

Attachments: File gradle-bug-1517.zip    


Trying to integrate a plugin with the apply from: syntax fails as the plugin cannot be found. It seems the apply statement is not using the classpath of the script to resolve the plugin, but should.

To reproduce, unzip the attached project, switch into the new directory and type

$ gradle build

FAILURE: Build failed with an exception.

  • Where:
    Script '/home/User/Documents/gradle-bug/plugin/simple.gradle' line: 8
  • What went wrong:
    A problem occurred evaluating script.
    Cause: Plugin with id 'simple' not found.
  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.


Comment by Eric Berry [ 25/Oct/11 ]

This bug is still present in milestone-5.

Comment by Denis Davydkov [ 09/Nov/11 ]

We faced with the same issue

Comment by npace [ 06/Feb/12 ]

Also bit by this in m7.

Comment by Adam Kaufman [ 07/Jan/14 ]

Just hit this today using 1.10

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 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.

Generated at Wed Jun 30 11:57:31 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.