anchor.diff:  
   Keep reading to learn how to adopt the configuration cache for your build or your plugins.
   
  -[[adoption]]
  +[[config_cache:adoption]]
   == Adoption steps
   
   An important prerequisite is to keep your Gradle and plugins versions up to date.
   The following explores the recommended steps for a successful adoption.
   It applies both to builds and plugins.
  -While going through these steps, keep in mind the HTML report and the solutions explained in the <<configuration_cache#requirements, requirements>> chapter below.
  +While going through these steps, keep in mind the HTML report and the solutions explained in the <<configuration_cache#config_cache:requirements, requirements>> chapter below.
   
   Start with `:help`::
   Always start by trying your build or plugin with the simplest task `:help`.
  
positive.code: 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]]
  == Not yet implemented
  
  Support for using configuration caching with certain Gradle features is not yet implemented.
  
negative.code: 
  Combining these two ways you can enable globally and disable for certain run configurations, or the opposite.
  
  [[config_cache:plugins]]
  == Supported plugins
  
  The configuration cache is brand new and introduces new requirements for plugin implementations.
  