In the native incremental compile tests (1), we're doing an initial compile, setting the last modified date to '0' for all compiled outputs, then compiling again. We can then check the last modified date to see which files were actually recompiled.
It's not particularly pretty, but it's working. Daz 1. org.gradle.nativebinaries.language.cpp.AbstractLanguageIncrementalCompileIntegrationTest On Thu, Apr 3, 2014 at 4:36 AM, Szczepan Faber < szczepan.fa...@gradleware.com> wrote: > Hey, > > How do we avoid sleeps in incremental compilation integ tests? My initial > batch of integ tests for java incremental compilation uses Thread.sleep and > file.lastModified to verify which files were actually recompiled. It seems > tricky to avoid the sleep. If I use file hash/size instead of lastModified > it does not work for cases where recompiled class is the same as the > original one. Another option would be to introduce some api/listener that > gets notified just before the compilation and receives the information > about requested source to compile. > > Thoughts? > > Cheers! > -- > Szczepan Faber > Principal engineer@gradle; Founder@mockito > Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: > http://www.gradlesummit.com >
