anchor.diff:  
   [[sec:task_configuration_avoidance_general]]
   === General
  +
   1. [[task_configuration_avoidance_guideline_use_help_task]] **Use `help` task as a benchmark during the migration.**
   The `help` task is the perfect candidate to benchmark your migration process.
   In a build that uses only the configuration avoidance API, https://scans.gradle.com/s/o7qmlmmrsfxz4/performance/configuration?openScriptsAndPlugins=WzFd[a build scan would show no tasks created immediately or created during configuration], and only the tasks that were actually executed would be created.
  
positive.code: ----
  =====
  ====
  In the future, Gradle will consider this sort of anti-pattern an error and will produce an exception.
  
  3. [[task_configuration_avoidance_guideline_prefer_small_incremental_change]] **Prefer small incremental changes.**
  
negative.code: 
  [NOTE]
  ====
  Although backward compatibility is good for users, we still recommended to upgrade to newer Gradle releases in a timely manner.
  This will reduce your maintenance burden.
  ====
  
  The first method to maintain compatibility is to compile your plugin against the Gradle 4.9 API and conditionally call the right APIs with Groovy (https://github.com/melix/jmh-gradle-plugin/blob/a034aa88805b7a06fa9c5a825d573554b2aa23e2/src/main/groovy/me/champeau/gradle/JMHPlugin.groovy#L289-L296[example]).
  