anchor.diff:  [.red]#✖#:: Unsupported plugin
   [.gray]#✖#:: Won't fix
   
  -[[community_plugins]]
  +[[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.
  
positive.code: org.gradle.unsafe.configuration-cache.max-problems=5
  ----
  
  [[invalidating_the_cache]]
  === 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.
  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.
  
negative.code: 
  Keep reading to learn how to tweak the configuration cache, manually invalidate the state if something goes wrong and use the configuration cache from an IDE.
  
  [[config_cache:usage:enable]]
  === Enabling the configuration cache
  
  By default, the configuration cache is not enabled.
  