anchor.diff:  * Create a new top level module named spring-cloud-starter-stream-source-foobar
   
   Please follow the instructions above for designing a proper Spring Cloud Stream Source. You may also look into the existing
  -starters for how to structure a new one. Ensure that you name the main `@Configuration` class of your starter as
  -`FoobarSourceConfiguration` as this is the default convention used by the app generation later. Please also make sure
  -that the package for this `@Configuration` is `org.springfamework.cloud.stream.app.foobar.source`. If you have a different
  -class/package name, see below for how to override that in the app generator. The functionality name for which you create
  +starters for how to structure a new one. The default naming for the main `@Configuration` class is
  +`FoobarSourceConfiguration` and the default package for this `@Configuration`
  +is `org.springfamework.cloud.stream.app.foobar.source`. If you have a different class/package name, see below for
  +overriding that in the app generator. The technology/functionality name for which you create
   a starter can be a hyphenated stream of strings such as in `scriptable-transform` which is a processor type in the
   module `spring-cloud-starter-stream-processor-scriptable-transform`.
   
  
positive.code: 
  If you only care about the foobar-source apps and nothing else, you can cd into those particular foo-bar-[binder]
  directories and import them directly into your IDE of choice. Each of them is a self contained spring boot application project.
  For all the generated apps, the parent is `spring-boot-starter-parent`. There is no way to change that around as ultimately these
  are spring boot based applications and that parent would bring many necessary spring components into your application.
  
  You can cd into these custom foobar-source directories and do the following to build the apps:
  
  
negative.code: * The patched copy of `jdbc-sink` application now includes `mysql` driver in it
  * This application can be run as standalone _uberjars_
  
  === Contributing Stream Application Starters and Generating Artifacts
  
  In this section, we will explain how to develop a custom source/sink/processor application and then generate
  maven and docker artifacts for it with the necessary middleware bindings using the existing tooling provided by the
  