anchor.diff:  [INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar
   ----
   
  -This line is extremely important
  +The following line is extremely important:
   
   [source,bash,indent=0]
   ----
   [INFO] Installing /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar to /path/to/your/.m2/repository/com/example/http-server/0.0.1-SNAPSHOT/http-server-0.0.1-SNAPSHOT-stubs.jar
   ----
   
  -It's confirming that the stubs of the `http-server` have been installed in the local repository.
  -
  -*run the integration tests*
  -
  -In order to profit from the Spring Cloud Contract Stub Runner functionality of automatic stub downloading you have to do the following in our consumer side project (`Loan Application service`).
  -
  -Add the `Spring Cloud Contract` BOM
  +It confirms that the stubs of the `http-server` have been installed in the local
  +repository.
  +
  +*Run the integration tests.*
  +
  +In order to profit from the Spring Cloud Contract Stub Runner functionality of automatic
  +stub downloading, you must do the following in your consumer side project (`Loan
  +Application service`):
  +
  +Add the `Spring Cloud Contract` BOM:
   
   [source,xml,indent=0]
   ----
  
positive.code: 	}
  ----
  
  This is because the builder is passed through callbacks to initalize it, so the SSL validation can be set up
  in the client at that point. This will happen automatically in your test if you are using the
  `@AutoConfigureWireMock` annotation (or the stub runner). If you are using the JUnit `@Rule` approach you need
  to add the `@AutoConfigureHttpClient` annotation as well:
  
  [source,java,indent=0]
  ----
  
negative.code: </plugin>
  ----
  
  IMPORTANT: This example uses "convention based" naming by setting the
  `packageWithBaseClasses` property. Doing so means that the two last packages combine to
  make the name of the base test class. In our case, the contracts were placed under
  `src/test/resources/contracts/fraud`. Since you do not have two packages starting from
  the `contracts` folder, pick only one, which should be `fraud`. Add the `Base` suffix and
  capitalize `fraud`. That gives you the `FraudBase` test class name.
  
  All the generated tests extend that class. Over there, you can set up your Spring Context
  or whatever is necessary. In this case, use http://rest-assured.io/[Rest Assured MVC] to
  start the server side `FraudDetectionController`.
  
  [source,java,indent=0]
  ----
  