anchor.diff:  
   The same requirement applies to dependency management types with some nuances.
   
  -Referencing heavyweight model objects such as `Configuration`, `Dependency`, `Publication` or `ArtifactResolutionQuery` is forbidden, more precise types must be used instead.
  +Referencing heavyweight model objects such as `Configuration`, `Dependency`, `Publication` or `ArtifactResolutionQuery` is disallowed, more precise types must be used instead.
   For example, if you reference a `Configuration` to later get the resolved files, you should instead declare a `FileCollection` as an input to your task.
   
  -Referencing dependency resolution results is also forbidden (e.g. `ArtifactResolutionQuery`, `ResolvedArtifact`, `ArtifactResult` etc...).
  +Referencing dependency resolution results is also disallowed (e.g. `ArtifactResolutionQuery`, `ResolvedArtifact`, `ArtifactResult` etc...).
   For example, if you reference some `ResolvedArtifactResult` instances, you should instead declare some `ArtifactCollection` as an input to your task.
  -The rule of thumb here is that tasks must not reference _resolved_ results, but lazy specifications instead, in order to do the dependency resolution at execution time.
  +The rule of thumb is that tasks must not reference _resolved_ results, but lazy specifications instead, in order to do the dependency resolution at execution time.
   
   Here's an example of a problematic task type referencing a `SourceSet`:
   
  
positive.code: [[plugin_support]]
  == Supported plugins
  
  The configuration cache is brand new and has strong requirements.
  As a result, both core Gradle plugins, and third party plugins need to be adjusted.
  This section provides information about the current support in <<configuration_cache#core_plugins, core Gradle plugins>> and <<configuration_cache#third_party_plugins, third party plugins>>.
  
  
negative.code: ====
  <1> no more problems reported, the `doLast {}` closure now only captures `classpath` which is of the supported `FileCollection` type
  
  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.
  