Am Sunday 04 April 2010 23:44:10 schrieb Adam Murdoch:
> On 3/04/10 3:55 AM, Spencer Allain wrote:
> > The "<<" form is confusing enough. Having the first hello world
> > example state that it's equivalent to doFirst will only lead to later
> > confusion once a user learns about doFirst and doLast.
>
> I think we should look at deprecating the '<<' form after the Gradle 0.9
> release. And possibly doFirst() and doLast() too, so that a task has
> only 1 action.
I vote against reducing the number of (possible) task-actions and against the
removal of doFirst() and doLast().
I don't know, whether I understand things right, I stored (in my mind) the
behaviour of task definitions that
task {
action
}
is run during configuration stage, and could be used to configure an existing
task (with the same name), whereas the task definition of
task << {
action
}
is a "real" task definition, which runs at execution stage and will fail, if a
task of the same name already exists.
I very appreciate both - doFirst() and doLast() - to extend an already
existing task. I beleive, that extending existing tasks with an userdefined
action is easier to understand or implement, than breaking up an existing
task-dependency graph and adding a completely new task at the right point.
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
