anchor.diff:  ====
   <1> no more problems reported, the `doLast {}` closure now only captures `classpath` which is of the supported `FileCollection` type
   
  -Note that sometime the disallowed type is indirectly referenced.
  +Note that sometimes the disallowed type is indirectly referenced.
   For example, you could have a task reference some type from a plugin that is allowed.
   That type could reference another allowed type that in turn references a disallowed type.
   The hierarchical view of the object graph provided in the HTML reports for problems should help you pinpoint the offender.
  
positive.code: ----
  
  The previous configuration cache entry could not be reused, and the task graph had to be calculated again.
  This is because we read the system property at configuration time, hence requiring to run the configuration phase again when the value of that property changes.
  Fixing that is as simple as wiring the system property directly, without reading it at configuration time.
  
  ====
  
negative.code: 
  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 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:
  
  