anchor.diff:  ----
   ====
   
  -If you used the Groovy DSL, you can see that all of the `producer()` parts of the Contract that were present in the
  +If you used the Groovy DSL, you can see that all the `producer()` parts of the Contract that were present in the
   `value(consumer(...), producer(...))` blocks got injected into the test.
   If you use YAML, the same applies for the `matchers` sections of the `response`.
   
  
positive.code: It was created by https://twitter.com/mgrzejszczak[Marcin Grzejszczak] and https://twitter.com/jkubrynski[Jakub Kubrynski]
  from (https://github.com/Codearte[Codearte]).
  
  The `0.1.0` release took place on 26 Jan 2015 and it became stable with `1.0.0` release on 29 Feb 2016.
  
  [[getting-started-introducing-spring-cloud-contract-why]]
  ==== Why Do You Need It?
  
negative.code: 
  - To ensure that HTTP and messaging stubs (used when developing the client) do exactly
  what the actual server-side implementation does.
  - To promote the ATDD (acceptance test-driven development) method, and the microservices architectural style.
  - To provide a way to publish changes in contracts that are immediately visible on both sides.
  - To generate boilerplate test code to be used on the server side.
  
  