anchor.diff:  In this case, leave the `Templates > Gradle` configuration untouched and edit each run configuration as you see fit.
   
   Combining these two ways you can enable globally and disable for certain run configurations, or the opposite.
  +
  +[TIP]
  +====
  +You can use the link:https://github.com/JetBrains/gradle-idea-ext-plugin[gradle-idea-ext-plugin] to configure IntelliJ run configurations from your build.
  +This is a good way to enable the configuration cache only for the IDE.
  +====
   
   [[config_cache:ide:eclipse]]
   === Eclipse IDEs
  
positive.code: When working on a plugin, progressively target the contributed or configured tasks.
  
  Explore by turning problems into warnings::
  Don't stop at the first build failure and <<configuration_cache#config_cache:usage:ignore_problems, turn problems into warnings>> to discover how your build or plugin behave.
  Use the HTML report to reason about the reported problems, read about them in the <<configuration_cache#config_cache:requirements, requirements>> and <<configuration_cache#config_cache:not_yet_implemented, not yet implemented>> sections below.
  Continue running more tasks.
  +
  This will give you a good overview of what problems your build or plugin is facing.
  Remember that when turning problems into warnings you might need to <<configuration_cache#config_cache:usage:invalidate, manually invalidating the cache>> in case of troubles.
  
  Step back and fix problems iteratively::
  
negative.code: 
  [IMPORTANT]
  ====
  This feature is currently *_highly experimental_* and not enabled by default.
  
  Not all <<configuration_cache#config_cache:plugins:core, core Gradle plugins>> are supported.
  Your build and the plugins you depend on might require changes to fulfil the <<configuration_cache#config_cache:requirements, requirements>>.
  