anchor.diff:  mvn clean install -Prest
   ```
   
  +== Standalone tests
  +
  +There is a integration test suite that downloads a wildfly server and deploys *hawkular-alerts* with an embedded
  +cassandra service.
  +These integration tests can be executed using *-Prest* profile:
  +
  +```shell
  +mvn clean install -Pstandalone
  +```
  +
   == Performance tests
   
   There is a performance test suite focus in the *hawkular-alerts-engine* project.
  
positive.code: 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 |
  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. +
  Main responsabilities are: +
  - Register at deployment time into the alerts-engine. +
  - Process actions messages with specific plugin semantic.
  |=======================
  
  == Getting started
  
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.
  