anchor.diff:  org.gradle.unsafe.configuration-cache.max-problems=5
   ----
   
  -[[invalidating_the_cache]]
  +[[config_cache:usage:invalidate]]
   === Invalidating the cache
   
   The configuration cache is automatically invalidated when inputs to the configuration phase change.
   But, you may have to manually invalidate the configuration cache when untracked inputs to the configuration phase change.
  -This can happen if you <<configuration_cache#ignore_problems,ignored problems>>, or when your build uses <<dynamic_versions#sec:dynamic_versions_and_changing_modules, dynamic dependency versions>> and remote dependencies changed for example.
  +This can happen if you <<configuration_cache#config_cache:usage:ignore_problems,ignored problems>>, or when your build uses <<dynamic_versions#sec:dynamic_versions_and_changing_modules, dynamic dependency versions>> and remote dependencies changed for example.
   See the <<configuration_cache#config_cache:requirements>> and <<configuration_cache#config_cache:not_yet_implemented>> sections below for more information.
   
   The configuration cache state is stored on disk in a directory named `.gradle/configuration-cache` in the root directory of the Gradle build in use.
  
positive.code: === Composite builds
  
  When using the configuration cache on a <<composite_builds#composite_builds,composite build>> a problem will be reported.
  If you <<configuration_cache#ignore_problems,ignore problems>> then the included builds will be skipped when reusing the configuration cache.
  
  See link:{gradle-issues}13503[gradle/gradle#13503].
  
  
negative.code: [.red]#✖#:: Unsupported plugin
  [.gray]#✖#:: Won't fix
  
  [[config_cache:plugins:community]]
  === Community plugins
  
  Please refer to issue link:{gradle-issues}13490[gradle/gradle#13490] to learn about the status of community plugins.
  