anchor.diff:  	</parent>
   ----
   
  -NOTE: You should only need to specify the Spring Boot version number on this dependency.
  +NOTE: You should need to specify only the Spring Boot version number on this dependency.
   If you import additional starters, you can safely omit the version number.
   
   With that setup, you can also override individual dependencies by overriding a property
  -in your own project. For instance, to upgrade to another Spring Data release train you'd
  -add the following to your `pom.xml`.
  +in your own project. For instance, to upgrade to another Spring Data release train, you would
  +add the following to your `pom.xml`:
   
   [source,xml,indent=0,subs="verbatim,quotes,attributes"]
   ----
  
positive.code: 	</build>
  ----
  
  Then you need to set a `spring.devtools.remote.secret` property, for example:
  
  [source,properties,indent=0]
  ----
  
negative.code: WARNING: Enabling `spring-boot-devtools` on a remote application is a security risk. You
  should never enable support on a production deployment.
  
  Remote devtools support is provided in two parts: a server-side endpoint that
  accepts connections and a client application that you run in your IDE. The server
  component is automatically enabled when the `spring.devtools.remote.secret` property
  is set. The client component must be launched manually.
  
  
  
  ==== Running the Remote Client Application
  The remote client application is designed to be run from within your IDE. You need to run
  `org.springframework.boot.devtools.RemoteSpringApplication` with the same classpath as
  the remote project that you connect to.
  The application's single required argument is the remote URL to which it connects.
  
  For example, if you are using Eclipse or STS and you have a project named `my-app` that
  you have deployed to Cloud Foundry, you would do the following:
  
  * Select `Run Configurations...` from the `Run` menu.
  * Create a new `Java Application` "`launch configuration`".
  