anchor.diff:  
   | `(no label)` or `EXECUTED`
   | Task executed its actions.
  -| 
  +|
   
   * Used whenever a task has actions and Gradle has determined they should be executed as part of a build.
   * Used whenever a task has no actions and some dependencies, and any of the dependencies are executed. See also <<sec:lifecycle_tasks>>.
  
positive.code: 
  
  | `@api:org.gradle.api.tasks.CompileClasspath[]`
  | `Iterable&lt;File&gt;`\*
  | An iterable of input files and directories that represent a Java compile classpath. This allows the task to ignore irrelevant changes that do not affect the API of the classes in classpath. The following kinds of changes to the classpath will be ignored: 
  
  * Changes to the path of jar or top level directories.
  * Changes to timestamps and the order of entries in Jars.
  
negative.code: [TIP]
  .Don't forget about the build phases
  ====
  A task has both configuration and actions. When using the `doLast`, you are simply using a shortcut to define an action. Code defined in the configuration section of your task will get executed during the configuration phase of the build regardless of what task was targeted. See <<build_lifecycle>> for more details about the build lifecycle.
  ====
  
  
  