anchor.diff:   * Progress bar and timer visually describe overall status
    * Parallel work-in-progress lines below describe what is happening now
   
  -==== Fine-grained Control of Warnings
  -
  -By default, to avoid bothering users, Gradle won't display all warnings (e.g. deprecation warnings). Instead, Gradle will collect them and render a summary at the end of the build:
  -
  -----
  -There're <number> deprecation warnings, which may break the build in Gradle 5.0. Please run with --warning-mode=all to see them.
  -----
  -
  -`--warning-mode=(all,summary,none)`::
  -Specifies which type of warnings to display.
  -+
  -Set to `all` to display all warnings.
  -+
  -Set to `summary` to suppress all warnings and display a summary at the end of the build.
  -+
  -Set to `none` to suppress all warnings, including the summary at the end of the build.
  -
  -
  -=== Execution Options
  +[[sec:command_line_execution_options]]
  +=== Execution options
   The following options affect how builds are executed, by changing what is built or how dependencies are resolved.
   
   `--include-build`::
  
positive.code: 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
  
  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.
  
  
negative.code: ++++
  
  [[sec:command_line_debugging]]
  === Debugging options
  
  `-?`, `-h`, `--help`::
  Shows a help message with all available CLI options.
  