anchor.diff:  | You can add your custom options as input properties or disable caching of Javadoc.
   |===
   
  -==== Caveats
  +[[sec:task_output_caching_known_issues_caveats]]
  +===== Caveats
   
   These issues may affect the number of cache hits you may get between machines.
   
  
positive.code: | Gradle currently tracks the major version of Java (6 vs 7 vs 8) that is used for compilation and test execution. If your build expects to use several minor releases (1.8.0_102 vs 1.8.0_25), Gradle will treat all of these as equivalent and re-use outputs from any minor version. In our experience, bytecode produced by each major version is functionally equivalent.
  | Manually add the full Java version as an input to compilation and test execution tasks.
  
  | Changes in Gradle's file encoding that affects the build script
  | Gradle can produce different task output based on the file encoding used by the JVM. Gradle will use a default file encoding based on the operating system if `file.encoding` is not explicitly set.
  | Set the UTF-8 file encoding on all tasks which allow setting the encoding. Use UTF-8 file encoding everywhere by setting `file.encoding` to `UTF-8` for the Gradle JVM.
  
  
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].
  
  