anchor.diff:  
   Upon failure to serialize the state required to run the tasks, an HTML report of detected problems is generated.
   The Gradle failure output includes a clickable link to the report.
  -This report is useful and allows to drill down into problems, understand what is causing them.
  +This report is useful and allows you to drill down into problems, understand what is causing them.
   
   Let's look at a simple example build script that contains a couple problems:
   
  
positive.code: Details can be found in the linked HTML report.
  The report displays the set of problems twice.
  First grouped by problem message, then grouped by task.
  The former allows to quickly see what classes of problems your build is facing.
  The latter allows to quickly see which tasks are problematic.
  In both cases you can expand the tree in order to discover where in the object graph is the culprit.
  
  [TIP]
  ====
  
negative.code: * Gradle model types
  * Dependency management types
  
  Live JVM state types (e.g. `ClassLoader`, `Thread`, `OutputStream`, `Socket` etc...) are simply disallowed.
  
  Gradle model types (e.g. `Gradle`, `Settings`, `Project`, `SourceSet`, `Configuration` etc...) are usually used to carry some task input that should be explicitly and precisely declared instead.
  
  