anchor.diff:  
   TIP: You need to have http://maven.apache.org/download.cgi[Maven installed locally]
   
  -_Producer_
  +====== Producer
   
   As a *producer* it's enough to alter the Spring Cloud Contract Verifier to provide the URL and the dependency
   of the JAR containing the contracts:
  
positive.code: 
  You can pass those values also via properties from your deployment pipeline.
  
  ===== Common repo with contracts
  
  Another way of storing contracts other than having them with the producer is keeping them in a common place.
  It can be related to security issues where the consumers can't clone the producer's code. Also if you keep
  
negative.code: include::{introduction_url}/samples/standalone/contracts/src/assembly/contracts.xml[indent=0]
  ----
  
  ===== Workflow
  
  The workflow would look similar to the one presented in the `Step by step guide to CDC`. The only difference
   is that the producer doesn't own the contracts anymore. So the consumer and the producer have to work on
   common contracts in a common repository.
  
  ====== Consumer
  
  When the *consumer* wants to work on the contracts offline, instead of cloning the producer code, the
  consumer team clones the common repository, goes to the required producer's folder (e.g. `com/example/server`)
  