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?
Those tasks can be called like any other task. I'm not sure though
what you mean with 'have dependencies'. When we say
dependencies {
compile "x:y:3.0.5"
}
this assigns a dependency to the compile configuration. There is also
a mapping which relates the compile configuration to the compile
task, which allows the compile task to say: Give me a list of the jar
files belonging to me.
This list of jar files can then be used by the task, for example for
passing it to the Ant javac task. But this list of jar files are not
really dependencies of the task.
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?
Yes it would. The current plugin system is basic.
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
