anchor.diff:  that is scans for file changes in the source directory and apply them directly into the target directory, which is
   suitable for console developing since it doesn't require the whole maven build to see the actual changes in the console UI.
   
  -== Linking Git Repos via Bower
  +=== Linking Git Repos via Bower
   
   If you want to use your local version of hawkular-ui-components, you can use the `link` profile and the
   https://oncletom.io/2013/live-development-bower-component/[bower link functionality]. In the hawkular-ui-components,
  
positive.code: 
  The general idea here being hawt.io UIs which are composed of plugins (that can swapped around like legos between the various UIs)
  
  == Maven Install
  
  The easiest way to build the console is to use maven (inside the `console` directory):
  
  
negative.code: The plugin system makes it easy to add/remove functionality (even dynamically).
  
  
  === Bower Component
  
  This git repository is published as bower component and consumed by the https://github.com/hawkular/hawkular/ui/console/README.adoc[Hawkular Console]. Assets such as html/css/images/javascript can be published.
  
  === Directory Structure
  
  *dist* - directory for  artifacts that need to published via bower package.
  
  