anchor.diff:  .api:org.gradle.caching.http.HttpBuildCache[]
   |===
   | Description | Impact | Workaround
  +
   | `--offline` is not honored for the remote build cache.
   | The built-in HTTP build cache ignores the offline flag.
   | To completely disable task output caching, use `--no-build-cache`.
  
positive.code:     api:org.gradle.testing.jacoco.tasks.JacocoReport[]
  * api:org.gradle.plugin.devel.tasks.ValidateTaskProperties[]
  
  NOTE: It's very important that a cacheable task has a complete picture of its inputs so that the results from one build can be safely re-used somewhere else.
  
  Missing task inputs can cause incorrect cache hits, where different results are treated as identical because the same cache key is used by both executions. Missing task outputs can cause build failures if Gradle does not completely capture all outputs for a given task.
  
  In order to ensure that the inputs and outputs are properly declared use integration tests (for example using TestKit) to check that a task produces the same outputs for identical inputs and captures all output files for the task.
  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, usability and performance of your build when using the build cache.
  These issues will be corrected as this feature becomes stable.
  
  Note that task output caching relies on <<sec:up_to_date_checks,incremental build>>.
  Problems which affect incremental build can also affect task output caching even if the affected tasks are not cacheable.
  Most issues can only cause problems if your build cache is populated by non-clean builds or caching has been enabled for unsupported tasks.
  For a current list of open problems with incremental builds see these
  https://github.com/gradle/gradle/issues?utf8=%E2%9C%93&amp;q=is%3Aopen%20label%3Aa%3Abug%20label%3Ain%3Aincremental-build%20[Github issues].
  
  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.
  
  ==== Correctness issues
  
  These issues may affect the correctness of your build when using the build cache. Please consider these issues carefully.
  
  
negative.code: 
  | Overlapping outputs.
  | If two cacheable tasks share an output directory, Gradle does not reliably cache the results from either task.
  More precisely, Gradle is not able to determine which outputs belong to which task and will possibly store the combined output of both tasks in the build cache.
  When loading from the build cache you can get the combined output when you expect a single output and vice versa.
  | Disable caching for both tasks. You can detect this situation by using https://github.com/gradle/gradle/blob/master/gradle/overlappingTaskOutputsStatsInit.gradle[this init script].
  
  