anchor.diff:  Running `gradle buildEnvironment` visualises the buildscript dependencies of the selected project, similarly to how `gradle dependencies` visualizes the dependencies of the software being built.
   
   ----
  -❯ gradle buildEnvironment
  +$ gradle buildEnvironment
   ----
   
   Running `gradle dependencyInsight` gives you an insight into a particular dependency (or dependencies) that match specified input.
   
   ----
  -❯ gradle dependencyInsight
  +$ gradle dependencyInsight
   ----
   
   Since a dependency report can get large, it can be useful to restrict the report to a particular configuration. This is achieved with the optional `--configuration` parameter:
  
positive.code: 
  Running `gradle help --task someTask` gives you detailed information about a specific task.
  
  ==== Example: Obtaining detailed help for tasks
  
  .Output of **`gradle -q help --task libs`**
  ----
  > gradle -q help --task libs
  include::{samplesPath}/userguide/tutorial/projectReports/taskHelp.out[]
  ----
  
  
negative.code: It is common in Gradle builds for the `build` task to designate assembling all outputs and running all checks.
  
  ----
  $ gradle build
  ----
  
  === Running applications
  