anchor.diff:  ==== Custom Dependency Management
   By default, the CLI uses the dependency management declared in `spring-boot-dependencies`
   when resolving `@Grab` dependencies. Additional dependency management, which overrides
  -the default dependency management, can be configured by using the `@DependencyManagementBom`
  -annotation. The annotation's value should specify the coordinates
  -(`groupId:artifactId:version`) of one or more Maven BOMs.
  +the default dependency management, can be configured by using the
  +`@DependencyManagementBom` annotation. The annotation's value should specify the
  +coordinates (`groupId:artifactId:version`) of one or more Maven BOMs.
   
   For example, consider the following declaration:
   
  
positive.code: [[cli-groovy-beans-dsl]]
  == Developing Applications with the Groovy Beans DSL
  Spring Framework 4.0 has native support for a `beans{}` "`DSL`" (borrowed from
  http://grails.org/[Grails]),  and you can embed bean definitions in your Groovy
  application scripts by using the same format. This is sometimes a good way to include
  external features like middleware declarations, as shown in the following example:
  
  [source,groovy,indent=0]
  ----
  
negative.code: [[cli-default-grab-deduced-coordinates]]
  ==== Deduced "`grab`" Coordinates
  Spring Boot extends Groovy's standard `@Grab` support by letting you specify a dependency
  without a group or version (for example, `@Grab('freemarker')`). Doing so consults Spring
  Boot's default dependency metadata to deduce the artifact's group and version. Note that
  the default metadata is tied to the version of the CLI that you use – it changes only when
  you move to a new version of the CLI, putting you in control of when the versions of your
  dependencies may change. A table showing the dependencies and their versions that are
  included in the default metadata can be found in the <<appendix-dependency-versions,
  appendix>>.
  
  
  
  [[cli-default-import-statements]]
  ==== Default Import Statements
  To help reduce the size of your Groovy code, several `import` statements are automatically
  included. Notice how the preceding example refers to `@Component`, `@RestController`, and
  `@RequestMapping` without needing to use fully-qualified names or `import` statements.
  
  TIP: Many Spring annotations work without using `import` statements. Try running your
  application to see what fails before adding imports.
  
  
  
  