anchor.diff:  ...
   ----
   
  -* Build and install the newly updated bom:
  -
  -`./mvnw clean install -pl :spring-cloud-stream-app-dependencies`
  -
  -* At this point, you are ready to generate the binder based spring boot apps for foobar-source. Go to the
  -`spring-cloud-stream-app-generator` module and start editing as below.
  -
  -The minimal configuration needed to generate the app is to add to plugin configuration in
  -spring-cloud-stream-app-generator/pom.xml. There are other plugin options that customize the generated applications
  -which are described in the plugin documentation (https://github.com/spring-cloud/spring-cloud-stream-app-maven-plugin).
  -A few plugin features are described below.
  -
  -[source,xml]
  -----
  -<generatedApps>
  -....
  -    <foobar-source />
  -....
  -</generatedApps>
  -----
  -
  -More information about the maven plugin used above can be found here:
  -https://github.com/spring-cloud/spring-cloud-stream-app-maven-plugin
  -
  -If you did not follow the default convention expected by the plugin of where it is looking for the main configuration
  -class, which is `org.springfamework.cloud.stream.app.foobar.source.FoobarSourceConfiguration`, you can override that in
  -the configuration for the plugin. For example, if your main configuration class is `foo.bar.SpecialFooBarConfiguration.class`,
  -this is how you can tell the plugin to override the default.
  -
  -[source,xml]
  -----
  -<foobar-source>
  -    <autoConfigClass>foo.bar.SpecialFooBarConfiguration.class</autoConfigClass>
  -</foobar-source>
  -----
  -
  -* Go to the root of the repository and execute the script: `./generateApps.sh`
  +* At the root of the repository build, install and generate the apps:
  +
  +`./mvnw clean install -PgenerateApps`
   
   This will generate the binder based foobar source apps in a directory named `apps` at the root of the repository.
   If you want to change the location where the apps are generated, for instance /tmp/scs-apps, you can do it in the
  
positive.code: [[customizing-binder]]
  ==== Using a different binder
  
  If you want to use one of the applications found in Spring Cloud Stream Application Starters and you want to use one of the predefined binders (i.e. Kafka or Rabbit), you can just use the prebuilt versions of the artifacts.
  But if you want to connect to a different middleware system, and you have a binder for it, you will create new artifacts.
  
  [source,xml]
  ----
  
negative.code: * The patched copy of `jdbc-sink` application now includes `mysql` driver in it
  * This application can be run as standalone _uberjars_
  
  === Creating New 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
  spring cloud stream app starter infrastructure. For explanation purposes, we will assume that we are creating a new
  source application for a technology named foobar.
  
  * Create a repository called foobar in your local github account
  
  * The root artifact (something like foobar-app-starters-build) must inherit from `app-starters-build`
  
  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. The default naming for the main `@Configuration` class is
  