anchor.diff:  and `:jar` being Copy-like tasks which are not cacheable since it is generally faster to execute them.
   
   [[sec:task_output_caching_details]]
  -==== Cacheable tasks
  +=== Cacheable tasks
   
   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
  
positive.code: It also doesn't make sense to make tasks cacheable that do not produce outputs or have no task actions.
  
  [[sec:task_output_caching_cacheable_3rd_party]]
  ===== Third party plugins
  
  There are third party plugins that work well with the build cache.
  The most prominent examples are the https://developer.android.com/studio/releases/gradle-plugin.html[Android plugin 3.1+] and the https://blog.gradle.org/kotlin-build-cache-use[Kotlin plugin 1.2.21+].
  
negative.code: 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
  
  These issues may affect the correctness of your build when using the build cache. Please consider these issues carefully.
  
  