anchor.diff:  NOTE: When https://github.com/gradle/gradle/issues/new?labels=in:build-cache[reporting issues with the build cache], please check if your issue is a known issue or related to a known issue.
   
   [[sec:task_output_caching_known_issues_correctness]]
  -===== Correctness Issues
  +===== Correctness issues
   
   These issues may affect the correctness of your build when using the build cache. Please consider these issues carefully.
   
  -.Correctness Issues
  +.Correctness issues
   
   |===
   | Description | Impact | Workaround
  
positive.code: Now we see that, instead of executing the `:compileJava` task, the outputs of the task have been loaded from the build cache.
  The other tasks have not been loaded from the build cache since they are not cacheable. This is due to
  `:classes` and `:assemble` being <<sec:lifecycle_tasks,lifecycle tasks>> and `:processResources`
  and `jar` being Copy-like tasks which are not cacheable since it is generally faster to execute them.
  
  [[sec:task_output_caching_details]]
  ==== Task Output Caching in Detail
  
  Since a task describes all of its inputs and outputs, Gradle can compute a _build cache key_ that uniquely defines the task's outputs based on its inputs.
  That build cache key is used to request previous outputs from a build cache or push new outputs to the build cache. If the previous build is already populated by someone else, e.g. your
  
negative.code: 
  
  [[sec:build_cache_known_issues]]
  === Known issues with built-in Build Caches
  
  The built-in build caches have some known issues which will be addressed in future releases.
  
  