anchor.diff:  A task must not use any `Project` objects at execution time.
   This includes calling `Task.getProject()` while the task is running.
   
  -Some cases can be fixed in the same way as the previous constraint.
  +Some cases can be fixed in the same way as the previous requirement.
   
   Otherwise, to fix, use <<custom_gradle_types#service_injection,injected services>> instead of the methods of `Project`:
   
  
positive.code: The configuration cache is automatically invalidated when inputs to the configuration phase change.
  But, you may have to manually invalidate the configuration cache when untracked inputs to the configuration phase change.
  This can happen if you <<configuration_cache#ignore_problems,ignored problems>>, or when remote dependencies changed for example.
  See the <<configuration_cache#constraints>> and <<configuration_cache#not_yet_implemented>> sections below for more information.
  
  The configuration cache state is stored on disk in a directory named `.gradle/configuration-cache` in the root directory of the Gradle build in use.
  If you need to invalidate the cache, simply delete that directory:
  
negative.code: 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.
  
  Problems displayed in the report have links to the corresponding <<configuration_cache#requirements,requirement>> where you can find guidance on how to fix the problem or to the corresponding <<configuration_cache#not_yet_implemented,not yet implemented>> feature.
  