# Provide richer alternatives to multiple task actions

**URL:** <https://discuss.gradle.org/t/provide-richer-alternatives-to-multiple-task-actions/254>\
**Category:** Old Forum Archive\
**Created:** [September 29, 2011, 3:07pm UTC](https://discuss.gradle.org/t/provide-richer-alternatives-to-multiple-task-actions/254 "2011-09-29T15:07:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hansd](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/hansd/32/3_2.png) [@hansd](https://discuss.gradle.org/u/hansd)\
**Post date:** [September 29, 2011, 3:07pm UTC](https://discuss.gradle.org/t/provide-richer-alternatives-to-multiple-task-actions/254/1 "2011-09-29T15:07:00Z")

</div>

summary: Introduce finalizer and initializer tasks as an alternative to doFirst amd doLast actions. status: Post 1.0 code: planned

With a simple DAG model (like Ant has) you can’t express that something should be done after a node is executed. In Gradle you can solve this ATM with the actions you append to a task. We want to introduce finalizer tasks to solve this in a better way. They provide a DAG instead of a list, have a proper API, can be excluded, have a description, … It will simplify our task model and yet make it more powerful.

The other limitations of actions is that they form an ordered list which does not provide the richness of a graph and you might have some ordering issues. By introducing initializer and finalizer tasks they will provide a nicer alternatives for those kind of problems.

---

<div class="post-metadata">

**Author:** ![vips](https://avatars.discourse-cdn.com/v4/letter/v/54ee81/32.png) [@vips](https://discuss.gradle.org/u/vips)\
**Post date:** [April 24, 2013, 7:01pm UTC](https://discuss.gradle.org/t/provide-richer-alternatives-to-multiple-task-actions/254/2 "2013-04-24T19:01:00Z")

</div>

Is this feature added to 1.5?