Benjamin Muschko wrote:
>
> The dependency needs to be applied before I run my plugin code because
> it's using it.
>
It's not possible to add build script dependencies programmatically with a
plugin, at least not without a class loader hack. You either have to specify
them in a build script's "buildscript {}" section (which gets special
treatment), or package them with the plugin.
Benjamin Muschko wrote:
>
> Yes, I am making the call in the plugin apply method. It doesn't look like
> the buildscript dependencies have been resolved at that point of time.
>
They have to be resolved at that point because the script is already
running.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer & Consultant, Gradleware
http://www.gradleware.com
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Defining-buildscript-dependency-in-custom-plugin-tp3620230p3634375.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
