On 20/09/2013, at 10:58 PM, Sergey <[email protected]> wrote:
> Task.finalizedBy is in action now, but seems that Gradle doesn't consider > that configured finalizer task[s] may change (e.g. bytecode instrumentation) > the finalizedTask.outputs.files... > And that eventually directs to a failed up-to-date check for finalized task. > Any comments ? This is true of any task that changes the output of another task in place, without copying it somewhere else. It's something we plan to improve at some point. In the meantime, you need to give each task its own output directory, or use a Task.doLast() action instead of a finalizer task. -- 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 eXchange 2013, Oct 28th in London, UK: http://skillsmatter.com/event/java-jee/gradle-exchange-2013
