anchor.diff:  
   === Basic Compile and Test
   
  -To build the source you will need to install
  -http://maven.apache.org/run-maven/index.html[Apache Maven] v3.0.6 or above and JDK {jdkversion}.
  +To build the source you will need to install JDK {jdkversion}.
   
   Spring Cloud uses Maven for most build-related activities, and you
   should be able to get off the ground quite quickly by cloning the
   project you are interested in and typing
   
   ----
  -$ mvn install -s .settings.xml
  -----
  -
  -NOTE: You may need to increase the amount of memory available to Maven by setting
  -a `MAVEN_OPTS` environment variable with the value `-Xmx512m -XX:MaxPermSize=128m`
  -
  -The `.settings.xml` is only required the first time (or after updates
  -to dependencies). It is there to provide repository declarations so
  -that those do not need to be hard coded in the project poms.
  +$ ./mvnw install
  +----
  +
  +NOTE: You can also install Maven (>=3.3.3) yourself and run the `mvn` command
  +in place of `./mvnw` in the examples below. If you do that you also
  +might need to add `-P spring` if your local Maven settings do not
  +contain repository declarations for spring pre-release artifacts.
  +
  +NOTE: Be aware that you might need to increase the amount of memory
  +available to Maven by setting a `MAVEN_OPTS` environment variable with
  +a value like `-Xmx512m -XX:MaxPermSize=128m`. We try to cover this in
  +the `.mvn` configuration, so if you find you have to do it to make a
  +build succeed, please raise a ticket to get the settings added to
  +source control.
   
   For hints on how to build the project look in `.travis.yml` if there
   is one. There should be a "script" and maybe "install" command. Also
   look at the "services" section to see if any services need to be
   running locally (e.g. mongo or rabbit).  Ignore the git-related bits
  -that you might find in "before_install" since they will be able git
  +that you might find in "before_install" since they're related to setting git
   credentials and you already have those.
   
  -If you need mongo, rabbit or redis, see the README in the https://github.com/spring-cloud-samples/scripts[scripts
  -demo repository] for
  -instructions. For example consider using the "fig.yml" with
  -http://www.fig.sh/[Fig] to run them in Docker containers.
  +The projects that require middleware generally include a
  +`docker-compose.yml`, so consider using
  +http://compose.docker.io/[Docker Compose] to run the middeware servers
  +in Docker containers. See the README in the
  +https://github.com/spring-cloud-samples/scripts[scripts demo
  +repository] for specific instructions about the common cases of mongo,
  +rabbit and redis.
  +
  +NOTE: If all else fails, build with the command from `.travis.yml` (usually
  +`./mvnw install`).
   
   === Documentation
   
  
positive.code: author credit if we do.  Active contributors might be asked to join the core team, and
  given the ability to merge pull requests.
  
  === Code Conventions and Housekeeping
  None of these is essential for a pull request, but they will all help.  They can also be
  added after the original pull request but before a merge.
  
negative.code: * Use the Spring Framework code format conventions. If you use Eclipse
    you can import formatter settings using the
    `eclipse-code-formatter.xml` file from the
    https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/master/spring-cloud-dependencies-parent/eclipse-code-formatter.xml[Spring
    Cloud Build] project. If using IntelliJ, you can use the
    http://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter
    Plugin] to import the same file.
  