Merge branch 'release/2.2.0' into develop
[DSI Releaser] prepare for next development iteration
[jvstm-cluster] Do not broadcast RemoteCommit when single node
[jvstm-datagrid] Remove experimental ispn datagrid impl
Support a clean shutdown for FenixFramework

  This feature updates the FenixFramework.shutdown() showdown hook with the
  minimal funcionality to support a clean shutdown and later allow for a new
  call to FenixFramework.initialize(Config).  For now, it sets 'initialized'
  to false, and additionally clears the cache(s).  The shutdown now also uses
  the INIT_LOCK to operate.

  This feature hasn't been thoroughly tested.  Nevertheless, it is fully
  functional in the RadarGun benchmark.
Merge pull request #156 from smmf/feature/clean-shutdown

Support a clean shutdown for FenixFramework
Upgrate to Java 7

  * Closes #151
[core-api] Bug Fix: Shutdown FenixFrameworkThread before the BackEnd shutdown

  * Closes #157
[archetype-clean] Updated Archetype

  * Now using the correct backend artifactId
  * Replaced slf4j-log4j with logback
  * AppName is now automatically inferred
  * Added Java 7 enforcing
[webapp-archetype-clean] Updated Archetype

  * Now using the correct backend artifactId
  * Replaced slf4j-log4j with logback
  * AppName is now automatically inferred
  * Added Java 7 enforcing
[module-archetype-clean] Added Java 7 Configuration
Merge pull request #161 from jcarvalho/fix/archetypes

Fixing Archetypes
Add backend-jvstm-lf-cluster

  This is a clustered implementation based on the lock-free JVSTM (>= 2.0).
  It will duplicate some code already implemented in jvstm-cluster and
  jvstm-datagrid.  Nevertheless, it is expected that this backend may
  supersede the jvstm-cluster backend, thus eliminating the duplication.  We
  chose to 'inherit' from jvstm-common instead of to create a jvstm-lf-common
  backend, because it is not expectable for this module to fully supersede the
  jvstm-common module, in the near future.
[jvstm-lf] Rename RemoteCommit to CommitRequest

  A CommitRequest is sent by every (write) transaction that needs to commit.
  It contains the read set and write set of the transaction to commit.  After
  this, every node can locally continue its commits starting from this queue.
[jvstm-lf] Update POMs with dependency on JVSTM 2.0 (lock-free)
[jvstm-lf] Upgrade from jvstm:jvstm:2.0 to jvstm:jvstm:2.1
[jvstm-lf] Updates just to allow compilation with JVSTM 2
[jvstm-lf] DRAFT: Milestone: Send CommitRequest
[jvstm-lf] DRAFT: Ongoing work in distributed commit

  * Improvements to the RemoteCommit, revise the validation algorithm, create
    Local- and Remote- LockFreeTransactions.  DistributedLockFreeTransaction
    is what actually is created by JVSTM's transaction factory. Then Local or
    Remote instances are created when processing the commit requests.  A
    LocalLockFreeTransaction wraps the node's local
    DistributedLockFreeTransaction instance.
[jvstm-lf] DRAFT: Ongoing work in distributed commit (before thinking of subclass for DistributedLFTx)

...which didn't happen