anchor.diff:  This will force `test` and _all_ task dependencies of `test` to execute. It's a little like running `gradle clean test`, but without the build's generated output being deleted.
   
   [[sec:continue_build_on_failure]]
  -==== Continuing the Build When a Failure Occurs
  +==== Continuing the build when a failure occurs
   
   By default, Gradle will abort execution and fail the build as soon as any task fails. This allows the build to complete sooner, but hides other failures that would have occurred. In order to discover as many failures as possible in a single build execution, you can use the `--continue` option.
   
  
positive.code: +
  Set to `verbose` to enable color and other rich output like the `rich`, but output task names and outcomes at the lifecycle log level, as is done by default in Gradle 3.5 and earlier.
  
  ==== Rich Console
  
  Gradle's rich console displays extra information while builds are running.
  
  image::img/rich-cli.png[alt="Gradle Rich Console"]
  
negative.code: 
  You can also specify `--distribution-type=(bin|all)`, `--gradle-distribution-url`, `--gradle-distribution-sha256-sum` in addition to `--gradle-version`. Full details on how to use these options are documented in the <<gradle_wrapper,Gradle wrapper section>>.
  
  === Environment options
  You can customize many aspects about where build scripts, settings, caches, and so on through the options below. Learn more about customizing your <<build_environment, build environment>>.
  
  `-b`, `--build-file`::
  