anchor.diff:  Custom task types are _not_ cacheable by default.
   
   [[sec:task_output_caching_cacheable_tasks]]
  -===== Built-in cacheable tasks
  +==== Built-in cacheable tasks
   
   Currently, the following built-in Gradle tasks are cacheable:
   
  
positive.code: 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
  
  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:task_output_caching_known_issues_caveats]]
  ==== Caveats
  
  These issues may affect the number of cache hits you get between machines.
  
  