Avoiding common pitfalls

A common mistake when creating a task and adding actions for this task is that we forget the left-shift operator (<<). Then we are left with a valid syntax in our build script, so we don't get an error when we execute the task. However, instead of adding actions, we have configured our task. The closure we use is then interpreted as a configuration closure. All methods and properties in the closure are applied to the task. We can add actions for our tasks in the configuration closure, but we must use the doFirst and doLast methods. We cannot use the left-shift operator (<<).

The following tasks do the same thing, but note the subtle differences when we define the tasks:

def printTaskName = { task -> 
    println "Running ${task.name}" 
} 
 
task 'one' { 
    // Invoke doFirst method to add action. 
    doFirst printTaskName 
} 
 
// Assign action through left-shift operator (<<). 
task 'two' << printTaskName 
 
task 'three' { 
    // This...