Upgrade to Advice-1.5

  * Atomic annotation no longer uses the `adviceFactory` property
Create atomic-maven-plugin

  * Move the processing of the atomic annotation to a specific mojo.
  * Closes #78
Move Atomic annotation to core module

  * this eliminates all the indirections in the use of AtomicContexts
  * now, the FF strictly enforces the AtomicContext to execute
    TxManager.withTransaction.  As before, each backend specifies how the
    method withTransaction should behave.
  * Closes #70
Create ff-maven-plugin

  * This plugin is a simple facade that provides goals from both the
    dml-maven-plugin and the atomic-maven-plugin.  The idea is that
    programmers using the Fenix Framework should only need to use this plugin.
    The goals it provides have the same name as the goals that already
    existed, but with the `ff-` prefix.  Currently, there are the following
    goals:

      * ff-generate-domain
      * ff-post-compile
      * ff-process-atomic-annotations
      * ff-test-generate-domain
      * ff-test-post-compile
      * ff-test-process-atomic-annotations

   * There is some redundancy in that the new adapter Mojos, created in the
     ff-maven-plugin, need to declare the same parameters as the ones that
     they extend.  This can be avoided by building our Mojos using Java 5
     annotations for plugin parameters instead of the Javadoc annotations
     (http://jira.codehaus.org/browse/MPLUGIN-189).

   * Add pt.ist.fenixframework.core.ProcessAtomicAnnotations

   * Update README.md to reflect the latest changes.
Merge pull request #81 from smmf/feature/atomic-annotation-refactorings

feature/atomic-annotation-refactorings:

  * Upgrade to Advice-1.5
  * Create atomic-maven-plugin
  * Move Atomic annotation to core module
  * Create ff-maven-plugin

Details on each feature are in their respective commit logs.

**Important note**: The dml-maven-plugin no longer processes the Atomic annotation. There is a dedicated plugin for that. There is also the ff-maven-plugin that aggregates all plugin functionality in the FF. This is what the end programmer should use. Changes required to use this new version:

  * replace dml-maven-plugin with ff-maven-plugin in end user applications
  * the goal names are the same, but prefixed with ff-, e.g. ff-generate-domain.