anchor.diff:  {gradle-user-guide}/userguide.html[various IDEs].
   
   TIP: If you accidentally run a web application twice, you see a "`Port already in use`"
  -error. STS users can use the `Relaunch` button rather than the `Run` button to ensure that
  -any existing instance is closed.
  +error. STS users can use the `Relaunch` button rather than the `Run` button to ensure
  +that any existing instance is closed.
   
   
   
  
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 `org.springframework.boot` and `java` plugins and is shown in the following example:
  
  [indent=0,subs="attributes"]
  ----
  	$ gradle bootRun
  ----
  
  You might also want to use the `JAVA_OPTS` operating system environment variable, as shown
  in the following example:
  
  [indent=0,subs="attributes"]
  ----
  
negative.code: ----
  
  If the class is not on the classpath, you can use the `excludeName` attribute of the
  annotation and specify the fully qualified name instead. Finally, you can also control
  the list of auto-configuration classes to exclude by using the
  `spring.autoconfigure.exclude` property.
  
  TIP: You can define exclusions both at the annotation level and by using the property.
  
  [[using-boot-spring-beans-and-dependency-injection]]
  == Spring Beans and Dependency Injection
  You are free to use any of the standard Spring Framework techniques to define your beans
  and their injected dependencies. For simplicity, we often find that using
  `@ComponentScan` (to find your beans) and using `@Autowired` (to do constructor
  injection) works well.
  
  If you structure your code as suggested above (locating your application class in a root
  package), you can add `@ComponentScan` without any arguments. All of your application
  