anchor.diff:  // See the License for the specific language governing permissions and
   // limitations under the License.
   
  -[[avoiding_task_configuration]]
  -== Avoiding Task Configuration
  -
  -We are asking early adopters to try out a new API for creating and configuring tasks to iron out any issues and gather feedback. This chapter provides a quick introduction to the feature and explains some guidelines for migrating your build to use the new API. We intend for this new API to replace the existing API through our usual deprecation process over several releases.
  +[[task_configuration_avoidance]]
  +== Task Configuration Avoidance
  +
  +We are asking early adopters to try out a new API for creating and configuring tasks to iron out any issues and gather feedback. This chapter provides a quick introduction to the feature and explains some guidelines for migrating your build to use the new API. We intend for this new API to eventually replace the existing API through our usual deprecation process over several major releases.
   
   [NOTE]
   ====
  
positive.code: 
  | api:org.gradle.api.NamedDomainObjectCollection#findByName(java.lang.String)[]
  | No direct equivalent.
  2+| `named(String)` is the closest equivalent, but will fail if the task does not exist. Using `findByName(String)` will cause lazy tasks to be created/configured.
  
  | api:org.gradle.api.tasks.TaskContainer#findByPath(java.lang.String)[]
  | No direct equivalent.
  
negative.code: - Try your build with the latest nightly (see the version number at the top of this page).
  - How many tasks do you see registered with the new API?  See <<sec:how_do_i_know_its_working>> for how to find this.
  - Which task types do you have a lot of? Which ones are created with the old API? Which ones are registered with the new API, but have been created/configured anyways?
  - Following <<sec:task_configuration_avoidance_pitfalls>>, change your build scripts to use the new API to avoid creating/configuring tasks that are from the built-in Gradle plugins. Is there an impact to the number of tasks that are created?
  - Convert some of your custom plugins/tasks to use the new API.  Is there an impact to the number of tasks using the new API and the number of new API tasks that are created?
  - Run the https://github.com/gradle/gradle-profiler[gradle-profiler] to measure the difference between a build with less task configuration and a build where all tasks are configured. What do you see? Use <<sec:new_task_gradle_profiler_scenario,the scenario file below>>.
  
  [[sec:task_configuration_avoidance_guidelines]]
  === Guidelines
  
  [[sec:how_do_i_defer_creation]]
  