anchor.diff:  specified by the extension) is present under the `configuration` key.
   
   The optional `id` key is useful if there are multiple configuration sources (see
  -link:multi-file-configuration.html[multi file configuration] for example) as it affects how the configurations from the
  +<<Multi-file Configuration,multi file configuration>> for example) as it affects how the configurations from the
   different sources are merged together.
   
   ==== The Legacy JSON Configuration Format
  
positive.code: 
  There is a simpler way though.
  
  You can use the `versionFormat` link:../check-mojo.html#versionFormat[configuration parameter] to specify how the
  version string of the latest release must look like.
  
  For example if you use "GA" as the suffix of your final releases and you released `1.0.GA`, `2.0.Alpha` and `2.0.Beta`,
  
negative.code: plugin will break the build if such differences are found since the last released version.
  
  One then has to somehow "persuade" the plugin to let the build pass again. One way of doing it is to use the
  link:../revapi-basic-features/extensions/ignore.html[ignore extension] and list all the changes and provide them
  with a "justification" for why such change happened.
  
  This is very rigorous but also laborious approach that isn't always worth the effort - especially in the early stages
  