On May 28, 2008, at 9:10 AM, Ittay Dror wrote:
hdockter wrote:
I'm looking forward to implementing this. This is just a rough
outline. Any feedback is very welcome.
If A plugin adds tasks (targets) to the project, can't they then be
called
like any other task, have dependencies, etc?
A question about plugins is the use of the convention object. It
looks like
currently there can only be one convention object (JavaPlugin does
'project.convention = javaConvention' and if convention exists,
leave it as
is). Wouldn't this create conflicts when multiple plugins are used?
This problem is solved in Gradle 0.2. See UG 8.2.1.
- Hans
Ittay
--
View this message in context: http://www.nabble.com/The-new-Gradle-
plugin-system-tp17239360p17506455.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
