On May 29, 2008, at 8:22 AM, Ittay Dror wrote:
One thing I find great in Maven is the way plugins are just another
type of
dependency that Maven downloads and uses automatically. As more and
more
plugins are used in a build environment, it becomes more cumbersome
to tell
the developers to download and drop them in the right directory them
manually.
So, why not use the artifact identification for plugins and let gradle
download them automatically using ivy? something like
plugin('org.gradle:java')? (there's no version on purpose, this
means use
latest). Gradle can still be shipped with a default plugin
repository, and
maybe maintain the ability to use classes directly (plugin(class:
MyPlugin)), for ad-hoc plugins.
I agree. This is a feature we want to have for our new plugin system.
- Hans
Ittay
--
View this message in context: http://www.nabble.com/The-new-Gradle-
plugin-system-tp17239360p17528003.html
Sent from the gradle-dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
