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: * a copy of the console problem report, or ideally the HTML problem report you got, so the plugin author can easily reason about the problems,
  * ideally a reproducer build, so the plugin author can easily reproduce the problems.
  
  [[config_cache:testing]]
  == Testing your build logic
  
  
negative.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 and plugins behave.
  If a build fails, use the HTML report to reason about the reported problems related to the failure.
  Continue running more useful tasks.
  +
  This will give you a good overview of the nature of problems your build and plugins are 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::
  