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 ?



--
View this message in context: 
http://gradle.1045684.n5.nabble.com/Running-a-task-after-execution-of-another-task-tp4405504p5711886.html
Sent from the gradle-user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to