anchor.diff:  The goal is to have only a single lock file per project, which contains the lock state for all configurations of said project.
   By default, the file is named `gradle.lockfile` and is located inside the project directory.
   The lock state for the buildscript itself is found in a file named `buildscript-gradle.lockfile` inside the project directory.
  +
  +[NOTE]
  +====
  +It is impossible to leverage the single lockfile format for the settings configurations locking, because feature previews are applied after Gradle settings are configured.
  +====
   
   The main benefit is a substantial reduction in the number of lock files compared to the format requiring one lockfile per locked configuration.
   
  
positive.code: 
  Lock state will be preserved in a file located in the folder `gradle/dependency-locks` inside the project or subproject directory.
  Each file is named by the configuration it locks and has the `lockfile` extension.
  The one exception to this rule is for configurations for the <<plugins.adoc#sec:applying_plugins_buildscript,buildscript itself>>.
  In that case the configuration name will be prefixed with `buildscript-`.
  
  The content of the file is a module notation per line, with a header giving some context.
  Module notations are ordered alphabetically, to ease diffs.
  
negative.code: include::sample[dir="snippets/dependencyManagement/dependencyLocking-lockingClasspathConfiguration/kotlin",files="build.gradle.kts[tags=locking-classpath]"]
  ====
  
  Produced lockfiles will have a `buildscript-` prefix to their name to prevent any name collision with locking of regular project configurations.
  
  === Locking settings classpath configuration
  
  By doing the same as above in your <<build_lifecycle.adoc#sec:settings_file,Gradle settings file>>, you can lock the settings `classpath` configuration or any custom configuration you resolve as part of the settings.
  Produced lockfiles will have a `settings-` prefix to their name to prevent any name collision with either project configurations or project buildscript ones.
  
  == Generating and updating dependency locks
  
  In order to generate or update lock state, you specify the `--write-locks` command line argument in addition to the normal tasks that would trigger configurations to be resolved.
  