anchor.diff:  In general, you should avoid reading files at configuration time, to avoid invalidating configuration cache entries when the file content changes.
   Instead, you can connect the `Provider` returned by link:{javadocPath}/org/gradle/api/provider/ProviderFactory.html#fileContents-org.gradle.api.file.RegularFile-[providers.fileContents()] to task properties.
   
  -[[not_yet_implemented]]
  +[[config_cache:not_yet_implemented]]
   == Not yet implemented
   
   Support for using configuration caching with certain Gradle features is not yet implemented.
  
positive.code: // TODO java serialization support
  // TODO value suppliers reference documentation
  
  == Introduction
  
  The configuration cache is a feature that significantly improves build performance by caching the result of the <<build_lifecycle#build_lifecycle,configuration phase>> and reusing this for subsequent builds.
  
negative.code: - All tasks run in parallel by default.
  - Dependency resolution is cached.
  
  [[config_cache:usage]]
  == Using the configuration cache
  
  It is recommended to get started with the simplest task invocation possible.
  