anchor.diff:  === Undeclared reading of files
   
   Plugins and build scripts should not read files directly using the Java, Groovy or Kotlin APIs at configuration time.
  -Instead, declare files as potential build inputs using the value supplier APIs.
  +Instead, declare files as potential build configuration inputs using the value supplier APIs.
   
   This problem is caused by build logic similar to this:
   
  
positive.code: === Undeclared reading of system properties
  
  Plugins and build scripts should not read system properties directly using the Java APIs at configuration time.
  Instead, these system properties must be declared as a potential build input by using the value supplier APIs.
  
  This problem is caused by build logic similar to this:
  
  
negative.code: This means you will not see any build performance improvement the first time you run a particular set of tasks.
  
  When you subsequently run Gradle with this same set of tasks, for example by running `gradlew check` again, Gradle will load the tasks and their configuration directly from the configuration cache and skip the configuration phase entirely.
  Before using a configuration cache entry, Gradle checks that none of the "build configuration inputs", such as build scripts, for the entry have changed.
  If a build configuration inputs has changed, Gradle will not use the entry and will run the configuration phase again as above, saving the result for later reuse.
  
  Build configuration inputs include:
  
  - Init scripts, settings scripts, build scripts.
  - System properties, Gradle properties and configuration files used during the configuration phase, accessed using value suppliers such as providers for properties, environment variables etc...
  - Build configuration inputs and source files for `buildSrc` projects.
  
  === Performance improvements
  
  