anchor.diff:  [[sec:build_script_external_dependencies]]
   == External dependencies for the build script
   
  -If your build script needs to use external libraries, you can add them to the script's classpath in the build script itself. You do this using the `buildscript()` method, passing in a closure which declares the build script classpath.
  +If your build script needs to use external libraries, you can add them to the script's classpath in the build script itself. You do this using the `buildscript()` method, passing in a block which declares the build script classpath.
   
   .Declaring external dependencies for the build script
   ====
  
positive.code: 
  or
  
  .Using Groovy in Gradle's tasks
  ====
  include::sample[dir="userguide/tutorial/count/groovy", files="build.gradle[]"]
  include::sample[dir="userguide/tutorial/count/kotlin", files="build.gradle.kts[]"]
  
negative.code: ----
  ====
  
  What's going on here? This build script defines a single task, called `hello`, and adds an action to it. When you run `gradle hello`, Gradle executes the `hello` task, which in turn executes the action you've provided. The action is simply a block containing some code to execute.
  
  If you think this looks similar to Ant's targets, you would be right. Gradle tasks are the equivalent to Ant targets, but as you will see, they are much more powerful. We have used a different terminology than Ant as we think the word _task_ is more expressive than the word _target_. Unfortunately this introduces a terminology clash with Ant, as Ant calls its commands, such as `javac` or `copy`, tasks. So when we talk about tasks, we _always_ mean Gradle tasks, which are the equivalent to Ant's targets. If we talk about Ant tasks (Ant commands), we explicitly say _Ant task_.
  
  [[sec:build_scripts_are_code]]
  == Build scripts are code
  
  Gradle's build scripts give you the full power of Groovy and Kotlin. As an appetizer, have a look at this:
  
  .Using Groovy or Kotlin in Gradle's tasks
  ====
  include::sample[dir="userguide/tutorial/upper/groovy", files="build.gradle[]"]
  include::sample[dir="userguide/tutorial/upper/kotlin", files="build.gradle.kts[]"]
  