On 26/04/2013, at 6:31 PM, Luke Daley <luke.da...@gradleware.com> wrote:
> http://forums.gradle.org/gradle/topics/replacing_tasks_overwrite_true_does_not_work_in_1_5 > > Overwriting tasks doesn't really work and I always steer people away from it. > > Do we plan to fix this or remove the feature? The long-term plan is to remove it. At this stage, the plan is to replace it with 2 things: - Defer inference of the 'how' until after we know the 'what'. In other words, don't create tasks for a domain object until after that domain object has been configured. - The ability to contribute to the 'how' for a 'what'. That is, you can state: in order to compile this executable, define these tasks. This gives us a strong relationship between a thing + action and the tasks that perform that action, rather than using task names to implicitly model this relationship. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
