anchor.diff:  dependencies to work with the library; see it as an opinionated view of what is required
   to get started.
   
  -Do not make assumptions about the project in which your starter is added . If the library
  +Do not make assumptions about the project in which your starter is added. If the library
   you are auto-configuring typically requires other starters, mention them as well. Providing
   a proper set of _default_ dependencies may be hard if the number of optional dependencies
   is high as you should avoid bringing unnecessary dependencies for a typical usage of the
  
positive.code: 
  [[boot-features-custom-starter-naming]]
  ==== Naming
  FPlease make sure to provide a proper namespace for your starter. Do not start your module
  names with `spring-boot`, even if you are using a different Maven groupId. We may offer an
  official support for the thing you're auto-configuring in the future.
  
  
negative.code: 
  * The `autoconfigure` module that contains the auto-configuration code.
  * The `starter` module that provides a dependency to the autoconfigure module as well as
    the library and any additional dependencies that are typically useful. In a nutshell,
    adding the starter should be enough to start using that library.
  
  TIP: You may combine the auto-configuration code and the dependency management in a single
  module if you don't need to separate those two concerns.
  