anchor.diff:  [[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>>.
  +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.
  +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.
   
   
   
  
positive.code:  ** Repositories
   * Active profiles
  
  See https://maven.apache.org/settings.html[Maven's settings documentation] for
  further information.
  
  
  
  [[cli-whats-next]]
  == What to Read Next
  There are some {github-code}/spring-boot-project/spring-boot-cli/samples[sample groovy
  scripts] available from the GitHub repository that you can use to try out the
  Spring Boot CLI. There is also extensive Javadoc throughout the
  {sc-spring-boot-cli}[source code].
  
  If you find that you reach the limit of the CLI tool, you probably want to look
  at converting your application to a full Gradle or Maven built "`Groovy project`". The
  next section covers Spring Boot's
  "<<build-tool-plugins.adoc#build-tool-plugins, Build tool plugins>>", which you can
  use with Gradle or Maven.
  
negative.code: 
  [partintro]
  --
  The Spring Boot CLI is a command line tool that you can use if you want to quickly develop
  a Spring application. It lets you run Groovy scripts, which means that you have a familiar
  Java-like syntax without so much boilerplate code. You can also bootstrap a new project or
  write your own command for it.
  --
  
  
  