Prevented memory leaks in the JVSTM/OJB Backend.
  * This commit mirrors 0b72f1f
Bug Fix: If the mojo cannot post process the classes, then build should be interrupted instead of continuing.
  * This commit mirrors 300f94
Allow VersionNotAvailableException to get passed a message that will be printed out with the stack trace.
  * This commit mirrors a192e24
Attempts to delete a connected domain object now state which role is the culprit.
  * This commit mirrors 2ad8ebb
Hot Fix: Connection pool now grows on exhaustion.
  * This commit mirrors 0c2f203
Minor Change: JDBC driver is now de-registered when the Framework is Shut Down.
Roles in a DomainRelation are now sorted, according to the role's name and class.
Changed the API to access the runtime Relations.

The breakdown is as follows:

  * The Relation fields generated in Base classes are no longer accessible.
  * Relations can now be accessed by calling X.getRelationY where X is the class name, and Y is the relation name.
  * The relation getter method is now generated in both ends of the relation, and returns the same object (thus allowing for relation listeners to be added in either side).
  * Removed the fields containing the inverseRelation. It is now invisible to the programmer which side is the direct and the inverse.
  * In the inverse side, the relation is accessed via the getter method, thus removing the need for the field.
  * The order of the relation no longer reflects the order of the 'playsRole' in the DML, and is now consistent with the role names.
Bugfix: Remove optimization in DirectRelation

  * When adding/removing to a relation, the commit
  d1cff4faf035c5874f24235639a1698e7bfbd883 was optimizing the operation, by
  checking whether the firstRole's add/remove had succeeded.  This was a
  problem when setting to null, because it would call add (on the role), which
  would return false (in case of a RoleMany), thus not running the add/remove
  for the other role, which was actually doing the add/remove.
Renamed 'getRelationSlotNameFor' to 'getRelationMethodNameFor'.
  * Relations are now accessed by a method instead of a field, change Code Generator
    method name to better reflect the new reality.
Merge pull request #69 from fenix-framework/feature/relation-api

New Relation API
Added DmlZipCreatorMojo.

  * This commit mirrors 9528b70
Merge pull request #72 from fenix-framework/feature/develop-merge

Merging Back Commits from Develop
Bug Fix: Relation slots are no longer kept in fields of the Base classes.
  * Relation slots are now lazy loaded using the Value Holder pattern
  * This commit addresses the problem presented in #75.
The Relation field in the internal Base class is now private.
Merge pull request #77 from fenix-framework/hotfix/relation-loading

Fixing Relation Loading Issues
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.