anchor.diff:  Use the built-in `gradle init` task to create a new Gradle builds, with new or existing projects.
   
   ----
  -❯ gradle init
  +$ gradle init
   ----
   
   Most of the time you'll want to specify a project type. Available types include `basic` (default), `java-library`, `java-application`, and more. See <<build_init_plugin.adoc#build_init_plugin, init plugin documentation>> for details.
   
   ----
  -❯ gradle init --type java-library
  +$ gradle init --type java-library
   ----
   
   === Standardize and provision Gradle
   The built-in `gradle wrapper` task generates a script, `gradlew`, that invokes a declared version of Gradle, downloading it beforehand if necessary.
   
   ----
  -❯ gradle wrapper --gradle-version=4.4
  +$ gradle wrapper --gradle-version=4.4
   ----
   
   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.adoc#gradle_wrapper,Gradle wrapper section>>.
  
positive.code: It is common for applications to be run with the `run` task, which assembles the application and executes some script or binary.
  
  ----
  ❯ gradle run
  ----
  
  === Running all checks
  
negative.code: Build scans give a full, visual report of what dependencies exist on which configurations, transitive dependencies, and dependency version selection.
  
  ----
  $ gradle myTask --scan
  ----
  
  This will give you a link to a web-based report, where you can find dependency information like this.
  