anchor.diff:  The build scan above shows that `:task1` and `:task3` could be improved and made cacheable
   and shows why Gradle didn't cache them.
   
  -== Configuration
  +== Optimize Configuration
   
   As described in <<build_lifecycle.adoc#build_lifecycle,the build lifecycle chapter>>, a
   Gradle build goes through 3 phases: initialization, configuration, and execution.
  
positive.code: 
  == Inspect your build
  
  Before you make any changes, <<inspect.adoc#build_scans,inspect your build>>. A proper build inspection helps
  you understand:
  
  - how long it takes to build your project
  
negative.code: NOTE: If you use annotation processors, you need to explicitly declare them in order for compilation avoidance to work.
  To learn more, check out the <<java_plugin.adoc#sec:java_compile_avoidance,compile avoidance documentation>>.
  
  == Optimize Android projects
  
  Everything on this page applies to Android builds, since Android builds use Gradle.
  Yet Android introduces unique opportunities for optimization.
  