anchor.diff:  	</dependencyManagement>
   ----
   
  -The preceding sample setup does not let you override individual dependencies by using a property, as
  -explained above. To achieve the same result, you need to add an entry in the
  -`dependencyManagement` of your project **before** the `spring-boot-dependencies`
  -entry. For instance, to upgrade to another Spring Data release train, you could add the
  -following element to your `pom.xml`:
  +The preceding sample setup does not let you override individual dependencies by using a
  +property, as explained above. To achieve the same result, you need to add an entry in the
  +`dependencyManagement` of your project **before** the `spring-boot-dependencies` entry.
  +For instance, to upgrade to another Spring Data release train, you could add the following
  +element to your `pom.xml`:
   
   [source,xml,indent=0,subs="verbatim,quotes,attributes"]
   ----
  
positive.code: 
  [[using-boot-running-with-the-gradle-plugin]]
  === Using the Gradle Plugin
  The Spring Boot Gradle plugin also includes a `bootRun` task that can be used to run
  your application in an exploded form. The `bootRun` task is added whenever you apply the
  the `org.springframework.boot` and `java` plugins and is shown in the following example:
  
  [indent=0,subs="attributes"]
  
negative.code: 	</build>
  ----
  
  Then you need to set a `spring.devtools.remote.secret` property, as shown in the following
  example:
  
  [source,properties,indent=0]
  ----
  