anchor.diff:  
   This would install the foo-source-kafka into your local maven cache (~/.m2 by default).
   
  -The app generation phase above would add an integration test to the app project that is making sure that all the spring
  +The app generation phase adds an integration test to the app project that is making sure that all the spring
   components and contexts are loaded properly. However, these tests are not run by default when you do a `mvn install`.
   You can force the running of these tests by doing the following:
   
  
positive.code: * 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
  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`.
  
  
negative.code: 
  * Go to the root of the repository and execute the script: `./generateApps.sh`
  
  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
  configuration section of the plugin.
  
  