anchor.diff:  ```
   skipper:>upgrade --release-name mylog --package-name log --package-version 2.0.0
   mylog has been upgraded.
  -Last Deployed: Sun Oct 08 00:04:48 EDT 2017
  -Status: mylog-v2.log[mylog-v2.log-0=deploying]
  +Last Deployed: Thu Oct 26 11:00:43 IST 2017
   ```
   
   You should see the java app named `log-sink-rabbit-1.2.0.RELEASE.jar` running in the output of the `jps` command.
  
positive.code: 
  Where you replace `/home/mpollack/` with your own home directory.
  
  The property `spring.cloud.skipper.server.synchonizeIndexOnContextRefresh` when set to `true` loads the packages from
   the configured `packageRepositories` during the server startup.
  
  Then launch the Skipper shell in another terminal
  
  ----
  $ java -jar spring-cloud-skipper-shell/target/spring-cloud-skipper-shell-1.0.0.BUILD-SNAPSHOT.jar
  ----
  
  The command `search` will seach for all available packages. It should then show you the following output
  
  ```
  skipper:>search
  ╔════════╤═══════╤═══════════════════════════════════════════════════════════════════════════╗
  ║  Name  │Version│                                Description                                ║
  ╠════════╪═══════╪═══════════════════════════════════════════════════════════════════════════╣
  ║log     │2.0.0  │The log sink uses the application logger to output the data for inspection.║
  ║log     │1.0.0  │The log sink uses the application logger to output the data for inspection.║
  ║log     │1.1.0  │The log sink uses the application logger to output the data for inspection.║
  ║ticktock│1.0.0  │The ticktock stream sends a time stamp and logs the value.                 ║
  ║time    │2.0.0  │The time source periodically emits a timestamp string.                     ║
  ╚════════╧═══════╧═══════════════════════════════════════════════════════════════════════════╝
  ```
  
  In another window you can run `watch -n 2 jps` so see which Java processes are running, since by default, the local deployer will be used to deploy packages.
  
negative.code: 
  Supported application types are Spring Boot applications.
  
  Supported Cloud Platforms are `Cloud Foundry`, `Kubernetes`.
  
  For development experience, `Local` deployment is supported.
  
  Skipper can be used as part of implementing the practice of Continuous Deployment.  It provides a versioned "single
  source of truth" that defines what applications were deployed to the cloud.  This enables easy rollbacks and upgrades without having to rebuild applications from source code.
  