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.
   
  +Alternatively, you can tell Gradle to rerun a specific task using the `--rerun` built-in <<#sec:task_options, task option>>.
  +
   [[sec:continue_build_on_failure]]
   === Continuing the build when a failure occurs
   
  
positive.code: include::{snippetsPath}/tutorial/projectReports/tests/taskHelp.out[]
  ----
  
  This information includes the full task path, the task type, possible command line options and the description of the given task.
  
  === Reporting dependencies
  
  
negative.code: 
  `-Dorg.gradle.java.home`::
  Set JDK home dir.
  
  [[sec:task_options]]
  == Task options
  
  Tasks may define task-specific options. Differently than most of the global options described in the sections above (which are interpreted by Gradle itself, can appear anywhere in the command line, and can be listed using the `--help` option),
  task options:
  
  1. are consumed and interpreted by the tasks themselves;
  2. *must* be specified immediately after the task in the command-line;
  3. may be listed using `gradle help --task someTask` (see <<#sec:show_task_details, Show task usage details>>).
  
  === Built-in task options
  
  Built-in task options are options available as task options for all tasks. At this time, the following built-in task options exist:
  
  `--rerun`::
  Causes the task to be re-run even if up-to-date. Similar to `<<#sec:rerun_tasks,--rerun-tasks>>`, but for a specific task.
  
  [[sec:command_line_bootstrapping_projects]]
  == Bootstrapping new projects
  