anchor.diff:  ----
   tasks.register "someTask"
   
  -tasks.register("aEagerTask") {
  +tasks.register("anEagerTask") {
       dependsOn someTask
   }
   ----
  
positive.code:     check.get().dependsOn verificationTask
  }
  ----
  Executing the `gradle check` task should execute `verificationTask`, but with this example, it won't.
  This is because the dependency between `verificationTask` and `check` only happens when `verificationTask` is realized.
  To avoid issues like this, you must only modify the task associated with the configuration action.
  Other tasks should be modified in their own configuration action outside of any other possibly "lazy" configuration actions.
  The code would become:
  +
  [source,groovy]
  ----
  def check = tasks.register("check")
  
negative.code: Because the task configuration action can now run immediately, later or never, mutating anything other than the current task will expose flaky-like behavior in your build.
  Consider the following code:
  +
  ====
  [.multi-language-sample]
  =====
  [source,groovy]
  ----
  def check = tasks.register("check")
  