anchor.diff:  m2-settings-repo-username: ciberkleid
   m2-settings-repo-password: my-super-secret-api-token
   
  -repo-with-binaries: https://ciberkleid@my-super-secret-api-token@dl.bintray.com/ciberkleid/maven-repo
  +repo-with-binaries: https://ciberkleid:my-super-secret-api-token@dl.bintray.com/ciberkleid/maven-repo
   
   repo-with-binaries-for-upload: https://api.bintray.com/maven/ciberkleid/maven-repo/fortune-service
   ```
  
positive.code: 
  Note that we are creating matching packages for the default, smoke, and e2e profiles only. We will address the package for the apicompatibility profile in Stage 3.
  
  When working with your own apps, if you have existing tests, you would now move them into one of these packages now, and rename them so that they are included in the filters declared in the profiles (i.e. the file names end in `Test.java` or `Tests.java`)
  
  In the case of our sample apps, there are no tests, so we add some now as follows.
  
  
negative.code: 
  *Edit smoke tests to align with the contract*
  
  Finally, we edit our smoke tests for `greeting-ui` to ensure the response does *not* contain the hystrix fallback, since we are now expecting a response from the stub.
  
  ```java
  package smoke;
  