anchor.diff:  (defaults to `${basedir}`, i.e. the root of the project). If there are
   any changes in the README it will then show up after a Maven build as
   a modified file in the correct place. Just commit it and push the change.
  -
  -=== Pull Requests
  -
  -Spring Cloud is released under the non-restrictive Apache 2.0 license,
  -and follows a very standard Github development process, using Github
  -tracker for issues and merging pull requests into master. If you want
  -to contribute even something trivial please do not hesitate, but
  -follow the guidelines below.
  -
  -==== Sign the Contributor License Agreement
  -Before we accept a non-trivial patch or pull request we will need you
  -to sign the
  -https://support.springsource.com/spring_committer_signup[contributor's
  -agreement].  Signing the contributor's agreement does not grant anyone
  -commit rights to the main repository, but it does mean that we can
  -accept your contributions, and you will get an 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.
  -
  -* Use the Spring Framework code format conventions. If you use Eclipse and you follow
  -  the ``Importing into eclipse'' instructions below you should get project specific
  -  formatting automatically. You can also import formatter settings using the
  -  `eclipse-code-formatter.xml` file from the `eclipse` folder. If using IntelliJ, you can
  -  use the http://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter Plugin]
  -  to import the same file.
  -* Make sure all new `.java` files to have a simple Javadoc class comment with at least an
  -  `@author` tag identifying you, and preferably at least a paragraph on what the class is
  -  for.
  -* Add the ASF license header comment to all new `.java` files (copy from existing files
  -  in the project)
  -* Add yourself as an `@author` to the .java files that you modify substantially (more
  -  than cosmetic changes).
  -* Add some Javadocs and, if you change the namespace, some XSD doc elements.
  -* A few unit tests would help a lot as well -- someone has to do it.
  -* If no-one else is using your branch, please rebase it against the current master (or
  -  other target branch in the main project).
   
   === Working with the code
   If you don't have an IDE preference we would recommend that you use
  
positive.code: 
  ==== Adding Project Lombok Agent
  
  Spring Cloud uses [Project
  Lombok](http://projectlombok.org/features/index.html) to generate
  getters and setters etc. Compiling from the command line this
  shouldn't cause any problems, but in an IDE you need to add an agent
  to the JVM. Full instructions can be found in the Lombok website. The
  sign that you need to do this is a lot of compiler errors to do with
  
negative.code: // Do not edit this file (e.g. go instead to docs/src/main/asciidoc)
  
  image::https://travis-ci.org/spring-cloud/spring-cloud-netflix.svg?branch=master[Build Status, link=https://travis-ci.org/spring-cloud/spring-cloud-netflix]
  
  