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: 
  == Building
  
  === 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 1.7.
  
  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.
  
  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
  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.
  
  === Documentation
  
  
negative.code: 	<dependencies>
  		<dependency>
  			<groupId>org.springframework.cloud</groupId>
  			<artifactId>spring-cloud-starter-config</artifactId>
  		</dependency>
  		<dependency>
  			<groupId>org.springframework.boot</groupId>
  