On Aug 14, 2009, at 12:29 PM, Jeppe Nejsum Madsen wrote:
Russel Winder <[email protected]> writes:
Is there a way plugins like this can be developed outside the Gradle
tree, i.e. as separate standalone entities.
Gradle will surely succeed far better if plugins were separate from
the
core, there could then be a community of plugins since people could
develop them and use them without having to work with the Gradle
source.
I agree completely. For know, I'm the only one able to build
releases of
our sw locally since I need to use a custom gradle version. Using the
buildSrc is one possible solution, but requires manual updates
Just an idea:
Would it be possible to specify a dependency in the buildscript
section
and later use it via useplugin? Ie something like
buildscript {
repositories {
gradlePlugins()
}
dependencies {
classpath 'myniceplugin:stuff:0.7'
}
}
usePlugin(stuff.MyPlugin)
That will work. What we still need is classloader isolation for
plugins and its internal dependencies.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
