anchor.diff:  
   Dependencies declared in a catalog are exposed to build scripts via an extension corresponding to their name.
   In the example above, because the catalog declared in settings is named `libs`, the extension is available via the name `libs` in all build scripts of the current build.
  -Declaring a dependency using the following notation:
  +Declaring dependencies using the following notation...
   
   .Dependency notation correspondance
   ====
  
positive.code: [[sub:version-catalog]]
  === Using a version catalog
  
  A _version catalog_ is a list of dependencies, represented as dependency coordinates only, that a user can pick from when declaring dependencies in a build script.
  
  For example, instead of declaring a dependency using a string notation, the dependency coordinates can be picked from a _version catalog_:
  
  
negative.code: 
  In the example above, any dependency which was using the `groovy` version as reference will be automatically updated to use `3.0.6`.
  
  NOTE: Again, overwriting a version doesn't mean that the actual _resolved_ dependency version will be the same: this only changes what is _imported_, that is to say what is used when declaring a dependency. The actual version will be subject to traditional conflict resolution, if any.
  
  [[sub:using-platform-to-control-transitive-deps]]
  == Using a platform to control transitive versions
  