anchor.diff:  $ java -jar ~/repo/spring-cloud-release-tools/spring-cloud-release-tools-spring/target/spring-cloud-release-tools-spring-1.0.0.BUILD-SNAPSHOT.jar --releaser.pom.branch=vDalston.SR1 --spring.config.name=releaser
   ----
   
  -The application will start running from your working directory.
  +The application will start running from your working directory. Running this code
  +follows the convention that you have the OAuth token environment variable set. It also assumes
  +that you might have some custom configuration in `config/releaser.yml` file. This setting is optional - if
  +you don't have that file, nothing will happen.
   
   TIP:  It is important that you clone the repository you are going to release using SSH in order for the
   `releaser` to be able to push tags and commit changes automatically.
  
positive.code: === Project options
  
  - `releaser.fixed-versions` - A String to String mapping of manually set versions. E.g. `"spring-cloud-cli" -> "1.0.0.RELEASE"` will set
  the `spring-cloud-cli.version` to `1.0.0.RELEASE` regardless of what was set in `spring-cloud-release` project
  - `releaser.git.clone-destination-dir` - Where should the Spring Cloud Release repo get cloned to. If null defaults to a temporary directory
  - `releaser.git.spring-cloud-release-git-url` - URL to Spring Cloud Release Git repository. Defaults to `https://github.com/spring-cloud/spring-cloud-release`
  - `releaser.git.oauth-token` - GitHub OAuth token to be used to interact with GitHub repo.
  
negative.code: $ ./mvnw clean install
  ----
  
  IMPORTANT: You must set the value of the OAuth token. You can do it either via
  the command line `--releaser.git.oauth-token=...` or put it as an env variable in `.bashrc`
  or `.zshrc` e.g. `export RELEASER_GIT_OAUTH_TOKEN=...`
  
  === How to run it (interactive mode)
  
  Go to your project (e.g. Spring Cloud Sleuth)
  