Adam Murdoch wrote > On 20/09/2013, at 10:58 PM, Sergey < > serzh.polyakoff@
> > 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 Maybe that would be interesting to somebody ... I've an example how to workaround this on compileJava & jibxBind pair sample. Note that this approach allows execute jibxBind & compileJava tasks both separately and in context of overall build process execution with correct up-to-date check and mutual dependency: -- View this message in context: http://gradle.1045684.n5.nabble.com/Running-a-task-after-execution-of-another-task-tp4405504p5711892.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
