anchor.diff:  Be aware of the <<sec:task_configuration_avoidance_pitfalls, common pitfall around deferred configuration>>.
   
   At this point, we should see a decent improvement regarding build configuration.
  -We recommend <<sec:how_do_i_know_its_working, profiling your build and note the improvement>>.
  +We recommend <<sec:new_task_gradle_profiler_scenario, profiling your build and note the improvement>>.
   Under some circumstance, you may <<task_configuration_avoidance_troubleshooting_no_improvement, notice no improvement>>.
   It’s unfortunate, and we feel your frustration. Keep reading onto the next section.
   
  
positive.code:   For example, https://github.com/gradle/gradle-native/issues/737[the issue of `FileCollection` using `TaskProvider` was a real discrepancy] found while migrating a build to lazy task API.
    As a rule of thumb, a `TaskProvider` should be accepted everywhere a `Task` instance is accepted.
  
  * **Where a task was resolved?**
  As we keep developing the feature, more reporting, and troubleshooting information will be made available to answer this question.
  In the meantime, https://gradle.com/enterprise/releases/2018.3#reduce-configuration-time-by-leveraging-task-creation-avoidance[build scan is the best way to answer this question].
  Follow these steps:
  
negative.code: [[sec:how_do_i_know_its_working]]
  ==== How do I know if it's working?
  
  https://scans.gradle.com/[Build scan] features specific information around task configuration avoidance.
  Navigating to the https://scans.gradle.com/s/yfkcpk4sflk32/performance/configuration[configuration tab under the performance card] gives https://scans.gradle.com/s/yfkcpk4sflk32/performance/configuration#summary-task-totals[task creation metrics].
  As you are migrating to the lazy task APIs, these metrics should evolve toward more task created during task graph calculation as well as an increase in the number of tasks not created.
  If you aren't seeing any improvement, have a look at the troubleshooting section <<task_configuration_avoidance_troubleshooting_where_resolved, Where a task was resolved?>>
  
  To approximate the time it takes to configure a build without executing tasks, you can run `gradle help`.
  Please use the Gradle Profiler to measure your build as described in <<sec:new_task_gradle_profiler_scenario>>.
  
  [[sec:task_configuration_avoidance_migration_guidelines]]
  === Migration Guide
  