Identify how incremental change behave when always out-of-date spec is present
lacasseio opened this issue · comments
As Nokee developer, I want to identify how incremental task change detection behaves when an always out-of-date spec is present, so that I can address #770.
Acceptance Criteria
- Does the out-of-date spec force the task to always be non-incremental?
The out-of-date spec will always force the task to be non-incremental, as will any other input properties. This is a limitation of Gradle's incremental build support. We will need to support our incremental build support. We need two kinds of incremental support: 1) detection when a full rebuild is required (discarding the previous state, mostly when building classpath changes), 2) detection of which files are removed, changed, or added from the input-derived data paths so we can keep the derived data directory up-to-date without losing Xcode incremental capability.