anchor.diff:  === Builds
   
   A build is an execution of a collection of tasks in a Gradle project.
  -You run a build via the CLI or an IDE by specifying task selectors. Gradle configures the build and selects the tasks to run.
  -Gradle runs the smallest complete set of tasks required from the requested tasks and their dependencies.
  +You run a build via the command line interface (CLI) or an IDE by specifying task selectors.
  +Gradle configures the build and selects the tasks to run.
  +Gradle runs the smallest complete set of tasks based on the requested tasks and their dependencies.
  
positive.code: 
  === Plugins
  
  Plugins provide a means of reusing logic and configuration across multiple projects.
  With plugins, you can write a task once and use it in multiple builds. Or you can store common configuration,
  like logging, dependencies, and version management, in one place. This reduces duplication in
  build scripts.
  
  === Build Phases
  
  
negative.code: Gradle makes common types of projects easy to build through conventions. Plugins set sensible defaults to keep build scripts minimal.
  But these conventions don't limit you: you can configure settings, add your own tasks, and make many other customizations in your builds.
  Extensibility::
  Most builds have special requirements that require custom build logic.
  You can readily extend Gradle to provide your own build logic with custom tasks and plugins.
  See Android builds for an example: they add many new build concepts such as flavors and build types.
  IDE support::
  