On Apr 16, 2009, at 12:12 PM, Adam Murdoch wrote:
Hans Dockter wrote:
On Apr 15, 2009, at 9:16 AM, Adam Murdoch wrote:
Hi,
I'm working on http://jira.codehaus.org/browse/GRADLE-269, which
is change the plugins to apply the convention mappings to all
Compile, Test, Jar, etc, tasks in the project, rather than just
those created by the plugin.
One thing I'm not sure of, is whether the mappings should be
applied only to those tasks created after the usePlugin() call, or
to all tasks created both before and after the plugin is applied.
Thoughts?
There is another aspect to this. Do we also want to allow an
(optional) plain construction of tasks without applying the plugin
configuration to them?
A good question. We possibly do. I'm not sure how important it is.
Along similar lines: do we want to allow some way to request that
the test convention mapping or the main convention mapping be applied?
I would think so. We need a generic mechanism when the type is not
enough information. Maybe some identifiers which are defined by the
plugin (e.g. 'test' in your example).
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
