anchor.diff:  == Initial Situation
   
   === Internal Project Dependencies
  -- frequent changes on patch or minor level for released versions
  -- the trunk of different projects use integration releases
  -- update is maintained manually
  -- small number of projects ( < 20 )
  +- Frequent changes on patch or minor level for released versions
  +- The trunks of different projects are using integration releases
  +- Update is maintained manually
  +- Small number of projects ( < 20 )
   
   === External Project Dependencies
  -- more than 100 dependencies in the platform project
  -- other projects have 25, 11 or none different dependencies
  -- conflicts between internal projects are possible
  -- updates are difficult, because there are a lot of transitive dependencies with conflicts
  +- More than 100 dependencies in the platform project
  +- Other projects have 25, 11 or none different dependencies.
  +- Conflicts between internal projects are possible.
  +- Updates are difficult, because there are a lot of transitive dependencies that may cause conflicts.
   
   == Requirements
   === Product or Internal Project Dependencies
  -- updates of internal should be maintained automatically
  -* based on a branch of the main product the version of the dependencies should be updated automatically and tested
  -* the update must consider the used version of the branch so that the main version always remains stable
  -* the order of versions must be correct handled
  -* it is necessary to support Subversion as well Git
  +- Updates of internal should be maintained automatically.
  +* Based on a branch of the main product the version of the dependencies should be updated automatically and tested
  +* The update must consider the used version of the branch. This ensures that the main version always remains stable.
  +* The order of versions must be handled correctly.
  +* Support of Subversion and Git is mandatory.
   
   .order of the ivy resolver for `1.0.+`
   ----
  
positive.code: . If the dependency is listed in the dependency filter the version is not used and
  .. an error is thrown.
  .. the version is taken from the filter configuration.
  . If the dependeny is a transitiv dependency of a configured dependency and the version does not match an error is thrown.
  
  I think all use cases are conceivable options. Therefore it should be configurable.
  
  - Which format should be used for lock files and configuration files?
  
  I think json format is readable and easy to use.
  
  == Workflow - Automatic Updates for Internal Dependencies
  .  triggered by new available release versions (Check repository for changes)
  .. https://marketplace.atlassian.com/plugins/com.entertainment.bamboo.plugins.httpclient/server/overview
  .. https://marketplace.atlassian.com/plugins/fr.armotic.bamboo.plugins.filedownloader/server/overview
  .. https://marketplace.atlassian.com/plugins/org.gaptap.bamboo.maven.maven-artifact-download-plugin/server/overview
  .. Implement own plugin for Bamboo
  . commit change to VCS, because the change must be used and the build takes more time
  . an automatic build is triggered by the change in the VCS
  . if the build fails a message must be sent to a group of people
  
  == Development Workflow - Update External Libraries
  . Project with dependency decleration can be used
  .. for testing dependencies
  .. analyzing transitiv dependencies
  .. the result of this project can be published to a local repository
  
  . The result from step 1 can be used in the real projects for testing.
  .. The update of this configuration should be supported by special gradle tasks.
  .. It should be possible to unlock the version in a special file, so that an automatic update is practicable.
  
  . After testing it is possible to use the same configuration for all projects.
  
  
negative.code:         latest: 1.0.1
  ----
  
  - A developer must be able to override these versions easily and reproducibly with a local version.
  ** This configuration must be handled in a separate file.
  ** The file *must not* be stored in the VCS. Furthermore, it must be possible to create a configuration in the VCS to prevent the storage at all.
  ** The handling should be supported by some helper tasks.
  - It must be possible to specify a version of a component or a version of a filter configuration.
  - The configuration of internal dependencies has to be configured in a separated file.
  
  === Standards Filter Formats
  - bom
  