anchor.diff:      dependsOn verificationTask
   }
   ----
  +=====
  +[.multi-language-sample]
  +=====
  +[source,kotlin]
  +----
  +val check = tasks.register("check")
  +val verificationTask = tasks.register("verificationTask") {
  +    // Configure verificationTask
  +}
  +check.configure {
  +    dependsOn(verificationTask)
  +}
  +----
  +=====
  +====
   In the future, Gradle will consider these flaky-mutations as failures.
   It also means the configuration needs to flow from the extensions to the tasks.
   Thus, the task should be configured by the extension and not the other way around.
  
positive.code: tasks.register "someTask"
  
  // Sometime later, an eager task is configured like
  task aEagerTask {
      // The task is resolved immediately as it will be treated as a property of the project and will result in an eager task lookup by name
      dependsOn someTask
  }
  
negative.code: ----
  tasks.register "someTask"
  
  tasks.register("anEagerTask") {
      dependsOn someTask
  }
  ----
  