On 23/02/10 6:38 PM, Peter Ledbrook wrote:
Yes, me again. Sorry. Another question derived from my Grails build
work: is it possible to augment the build classpath from plugins?
Possibly. What do you want to do exactly?
Let's say I have a Grails plugin that provides an extra Gradle task
for the build. This task requires an external dependency. Since it's a
task, that dependency needs to be on the build classpath.
When you say 'plugin', you mean a Grails plugin, rather than a Gradle
plugin, yes?
How does the whole process get kicked off? Is this from a Gradle plugin
which loads up the Grails plugins and does some stuff with them? Or some
other way?
In what form do you have the classpath for the Grails plugins and this
external dependency? A jar? Some Grails dependency definitions? A
ClassLoader?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
