anchor.diff:  The remote maven repositories need to be configured explicitly if the apps are resolved using maven repository except for `local` Data Flow server. The other
    Data Flow server implementations (that use maven resources for app artifacts resolution) have no default value for remote repositories.
    The `local` server has `https://repo.spring.io/libs-snapshot` as the default remote repository.
  - 
  +
   To pass the properties as commandline options:
   
   [source,bash]
  
positive.code: 
  NOTE: Similar to the `local-deployer` and `cloudfoundry-deployer` options as discussed above, there
  are equivalent settings available for Apache YARN, Apache Mesos and Kubernetes variants, too. Check out the
  respective link:https://github.com/spring-cloud?utf8=%E2%9C%93&query=deployer[SPI implementations] to 
  find out more details about the packages to configure for logging.
  
  === Application Logs
  
  The streaming applications in Spring Cloud Data Flow are Spring Boot applications and they can be 
  independently setup with logging configurations. 
  
  For instance, if you'd have to troubleshoot the `header` and `payload` specifics that are being passed
  around source, processor and sink channels, you'd be deploying the stream with the following
  
negative.code: [source,bash]
  ----
  dataflow:>stream deploy foo --properties "app.*.logging.level.org.springframework.integration=DEBUG"
  ----
  