anchor.diff:  	<dependencies>
   		<dependency>
   			<groupId>org.springframework.cloud</groupId>
  -			<artifactId>spring-cloud-starter</artifactId>
  +			<artifactId>spring-cloud-starter-config</artifactId>
   		</dependency>
   		<dependency>
   			<groupId>org.springframework.boot</groupId>
  
positive.code: ** `/refresh` for refreshing the `@RefreshScope` beans
  ** `/restart` for restarting the Spring context (disabled by default)
  ** `/pause` and `/resume` for calling the `Lifecycle` methods (`stop()` and `start()` on the `ApplicationContext`)
  * Bootstrap appplication context: a parent context for the main application that can be trained to do anything (by default it binds to the Config Server, and decrypts property values)
  
  == Quick Start
  
  
negative.code: 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]
  ----
  	$ ./mvnw eclipse:eclipse
  ----
  
  The generated eclipse projects can be imported by selecting `import existing projects`
  