anchor.diff:  Task types need to opt-in to task output caching using the `@api:org.gradle.api.tasks.CacheableTask[]` annotation.
   Note that `@api:org.gradle.api.tasks.CacheableTask[]` is not inherited by subclasses.
   Custom task types are _not_ cacheable by default.
  +
   Currently, the following built-in Gradle tasks are cacheable:
   
   * Java toolchain:
  
positive.code: |===
  
  [[sec:task_output_caching_known_issues_caveats]]
  ===== Caveats
  
  These issues may affect the number of cache hits you get between machines.
  
  
negative.code: We suggest adding tests to ensure that the task inputs are relocatable, i.e. that the task can be loaded from the cache into a different build directory (see `@api:org.gradle.api.tasks.PathSensitive[]`).
  
  [[sec:task_output_caching_known_issues]]
  === Feedback and known issues
  
  The task output caching feature has known issues that may impact the correctness of your build when using the build cache,
  and there are some caveats to keep in mind which may reduce the number of cache hits you get between machines.
  