[maven-release-plugin] prepare release v2.1.0-rc1
[maven-release-plugin] prepare for next development iteration
[jvstm-ojb] Bug Fix: Write transaction conflicts are now properly handled within withTransaction
[jvstm-ojb] Fixed the flattening of speculative read-only transactions

  * Write commands can now be flattened when the current transaction is
    running as speculative read-only.
  * This way, WriteOnReadErrors can now be detected by the outermost transaction,
    restarting it instead of only the inner transaction (which should be flattened)
[maven-release-plugin] prepare release v2.1.0-rc2
[maven-release-plugin] prepare for next development iteration
[Consistency Predicates] Bug Fix: Added escaping of table names in JDBC
queries inside JvstmOJBConsistencyPredicateSupport
[dml-maven-plugin] Bug Fix: Don't try to add artifacts without files to the compile classpath.

  * This caused a NPE when attempting to look for a Test Jar while in compile scope
Fixed compilation error introduced in 7d46a677dfc
[maven-release-plugin] prepare release v2.1.0
Merge branch 'release/2.1.0' into develop
[maven-release-plugin] prepare for next development iteration
[Consistency Predicates] Minor Change: Corrected package name in the
supported annotation types of the
ConsistencyPredicateAnnotationProcessor.
Closes #129
[Repository Bootstrap] Minor Change: Changed some logging information
from trace to info
Fix: initInstance hierarchy

  * This problem was detected after adding DomainBPlusTree.  Problem: there
    was a bug in the invocation of LeafNode.setEntries() from the constructor
    of LeadNode. When actually creating an instance of DomainLeafNode, it
    would invoke the override DomainLeafNode.setEntries(), which would attempt
    to access a yet uninitialized slot (domainEntries).  The solution is to
    change how initInstance happens by invoking it only once from the
    top-level AbstractDomainObject class, instead of invoking it once per
    class hierarchy level.