anchor.diff:  
   === Aggregate Report
   
  -NOTE: Goal details page: link:../report-aggregate-mojo.html[here]
  +NOTE: Goal details page: link:report-aggregate-mojo.html[here]
   
   For POM-packaged modules, one can create an aggregate report consisting of the individual reports of the modules that
   are (indirectly) referenced by the POM module. Again this can be configured the same way the rest of the Revapi goals.
  
positive.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
  
negative.code:   ...
  ```
  
  Notice that `revapi.ignore` doesn't contain the ``item``s defined in the parent POM. That is the default Maven behavior.
  To be able to inherit the configuration of the `revapi.ignore` extension from the parent POM, you have to specify
  how to merge the `item`s in the child POM like so:
  
  