anchor.diff:  eclipse. If you don't already have m2eclipse installed it is available from the "eclipse
   marketplace".
   
  +Unfortunately m2e does not yet support Maven 3.3, so once the projects
  +are imported into Eclipse you will also need to tell m2eclipse to use
  +the `.settings.xml` file for the projects.  If you do not do this you
  +may see errors many different errors related to the POMs in the
  +projects.  Open your Eclipse preferences, expand the Maven
  +preferences, and select User Settings.  In the User Settings field
  +click Browse and navigate to the Spring Cloud project you imported
  +selecting the `.settings.xml` file in that project.  Click Apply and
  +then OK to save the preference changes.
  +
  +NOTE: Alternatively you can copy the repository settings from https://github.com/spring-cloud/spring-cloud-build/blob/master/.settings.xml[`.settings.xml`] into your own `~/.m2/settings.xml`.
  +
   ==== Importing into eclipse without m2eclipse
   If you prefer not to use m2eclipse you can generate eclipse project metadata using the
   following command:
   
   [indent=0]
   ----
  -	$ mvn eclipse:eclipse
  +	$ ./mvnw eclipse:eclipse
   ----
   
   The generated eclipse projects can be imported by selecting `import existing projects`
  
positive.code:   other target branch in the main project).
  * When writing a commit message please follow http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html[these conventions],
    if you are fixing an existing issue please add `Fixes gh-XXXX` at the end of the commit
    message (where XXXX is the issue number).
  
negative.code: 
  === Basic Compile and Test
  
  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
  
  ----
  $ ./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're related to setting git
  credentials and you already have those.
  
  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: migration to the Maven wrapper (`.mvnw`) is underway. If you
  find a project that doesn't have it yet, raise an issue to get it
  added, and build with the command from `.travis.yml` (usually
  `mvn install -s .settings.xml`).
  
  === Documentation
  
  