[maven-release-plugin] prepare for next development iteration
Update .gitignore
Fix: correct logger message about GC vbodies
Extract method from TopLevelTransaction's validateCommitAndEnqueue

Extract method `enqueueValidCommit` from part of `validateCommitAndEnqueue`.
This enables subclasses to reuse most of the logic in the latter.
Add method to get the VBox's Inplace writes
Make TransactionSignaller.SIGNALLER public
Make ActiveTransactionsRecord's method 'trySetNext' public
Make TopLevelTransaction's 'validateCommitAndEnqueue' method protected
Enable getting the top-level transaction's ActiveTxRecord
Make TopLevelTransactions's method 'makeWriteSet' public
Add method setCommitTxRecord to TopLevelTransaction
Make TopLevelTransactions's method 'getWriteSet' public
Add method getCommitTxRecord. Refactor code in validateCommitAndEnqueue()
Transaction factory configures whether TopLevelTransaction should be reused.

  Retains the default behavior for the JVSTM, which is to reuse the TLT.
Extract methods from ReadWriteTransaction's 'getBoxValue' to enable reuse in subclasses
Merge pull request #7 from smmf/feature/be-friendlier-to-fenix-framework

Feature/be friendlier to fenix framework
Enable overriding the helpCommit operations (remove static modifier)
Update VBox's CASbody() to account for reloads

In the pure JVSTM the CAS can only fail because another thread already
committed this value.  However, when used together with Fenix Framework, it is
possible that the body changes because of reloads.  We identify this by
testing whether our commit did make it (this.body.version must be greater than
or equal to newValue.version).  If not, we retry the CAS.  This does not occur
in the pure JVSTM, which will just try the CAS once and even if it fails will
see the required body immediately.
Add missing initialization to inplace
Make Transactions's static method 'getRecordForNewTransaction' public