To me the way forward seems clear: - Provide additional TaskContainer.add methods that add and configure a task atomically. E.g. TaskContainer.add(name, type, closure)
- Guarantee that callbacks are only invoked after the task has been configured if an atomic add operation is used - Review plugins in the Gradle codebase to use atomic add operations whenever feasible Bottom line: When you can avoid having to deal with laziness, it's always a win. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Fwd-gradle-dev-Configuring-tasks-before-they-are-added-to-the-task-container-tp4875730p4876806.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
