anchor.diff:  
   Recommend using [autoenv](https://github.com/kennethreitz/autoenv) with a `.env` file at the root of the repo.
   
  -```bash
  +[source,]
  +[subs="verbatim,attributes"]
  +----
       ./gradlew release publishDocs -PbintrayUsername=$BINTRAY_USERNAME -PbintrayPassword=$BINTRAY_PASSWORD
       -PreleaseType=<MAJOR|MINOR|PATCH> -i
  -```
  +----
   
   The release steps are as follows:
   - check that the git workspace is clean
  
positive.code: - Make sure to check the 'use the default gradle wrapper' option.
  - First time build
  
  ```bash
  ./gradlew cleanIdea idea
  
  ```
  
  - To get more output from any gradle commands/tasks append a `-i` (info) or `-d` (debug) e.g.
  ```bash
  ./gradlew build -i
  
  ```
  - To publish to local maven repository
  ```bash
  ./gradlew clean build publishToMavenLocal -i
  
  ```
  
  NOTE: This build is optimized for releasing software to bintray/sonatype. In order for gradle to figure out
  the version the gradle plugin relies on local folder being a cloned git repository. Downloading the source archive
  
negative.code: ==== Snapshot
  
  This is normally done by the CI server
  [source,]
  [subs="verbatim,attributes"]
  ----
  ./gradlew snapshot -PbintrayUsername=<bintrayUsername> -PbintrayPassword=<bintrayPassword>
  ----
  
  ==== Override deploy
  
  To bypass the standard release flow and upload directly to bintray use the following task
  - manually set the version in version.properties
  [source,]
  [subs="verbatim,attributes"]
  ----
  ./gradlew clean build bintrayUpload -PbintrayUsername=$BINTRAY_USERNAME -PbintrayPassword=$BINTRAY_PASSWORD -PreleaseType=<MAJOR|MINOR|PATCH>
   --stacktrace
  ----
  
  ==== Releasing documentation
  
  To update the docs for an existing release pass the `updateMode` switch
  [source,]
  [subs="verbatim,attributes"]
  ----
  ./gradlew releaseDocs
  ----
  
  ==== Contributing
  
  