anchor.diff:  This component is responsible for the communication between the alerts engine and the bus. +
   *hawkular-alerts-engine* is decoupled from the bus, so it can be used in other scenarios +
   (i.e. standalone, third party alerts system).
  -| hawkular-actions-api |
  +| hawkular-alerts-bus-api |
  +This is the public API for message objects used in *hawkular-alerts-bus*. +
  +| hawkular-alerts-actions-api |
   Common API for action plugins. +
  -An action plugin will be deployed as a .war artifact and it will interact with the bus via this API.
  -| hawkular-actions-aerogear +
  -hawkular-actions-email +
  -hawkular-actions-sms +
  -hawkular-actions-snmp |
  -Project examples with the skeleton of a action plugin. +
  +An action plugin will be deployed as a .war artifact.
  +| hawkular-alerts-actions-bus |
  +Component responsible of the communication of the plugins with the engine via bus. +
  +It is used on bus deployments.
  +| hawkular-alerts-actions-standalone |
  +Component responsible of the communication of the plugins with the engine directly using Java API +
  +It is used on standalone deployments.
  +| hawkular-alerts-actions-plugins |
  +Alert actions plugins. +
   Main responsabilities are: +
  -- Register at deployment time into the alerts-engine. +
  -- Process actions messages with specific plugin semantic.
  +- Publish supported properties. +
  +- Process actions messages.
   |=======================
   
   == Getting started
  
positive.code: mvn clean install -Prest
  ```
  
  == Performance tests
  
  There is a performance test suite focus in the *hawkular-alerts-engine* project.
  
negative.code: mvn clean install -Pperf
  ```
  
  == Building REST API documentation
  
  REST API documentation can be generated using *-Pdocgen* profile. +
  The doc is generated under *hawkular-alerts-rest/target* folder.
  