'Release: update versions for modeshape-3.0.0.Final'
MODE-1703 fixed problems with invalid deserialization of Path and AddValueOperation, still doesn't solve problem as we start to get NullPointerException in ArrayOperation.mutableParent
Changed POM version to '3.0.1-SNAPSHOT'
Merge branch 'master' of git://github.com/kcrimson/modeshape into mode-1703
MODE-1703 Corrected serialization of Schematic deltas

Array objects were not being serialized/deserialized properly
within the delta's operation instances (e.g., PutOperation).

Normally, all SchematicEntry (e.g., Documents containing values
such as Arrays and other Documents) are serialized using BSON, and
this works correctly in the non-clustered case. However, in the
clustered case, the changes made to one Document are recorded to
create a SchematicEntryDelta that is shipped across the Infinispan
cluster. (This way we can ship only the changes to the
SchematicEntry rather than the whole document.) Thus the problem
only manifest itself in clustered configurations.

The actual problem stemmed from the fact that an
SchematicEntryDelta and its Operation objects are all
externalizable (with custom Externalizers). The Operation objects
can contain individual values, Document or Array objects. These are
also externalizable, but there was a single DocumentExternalizer
for both Document and Array objects and the DocumentExternalizer
wrote/read both to/from BSON.

However, the BSON format (which is simply a binary representation
of JSON documents, with a few extra value types) is only valid for
Documents; a standalone Array cannot be written in BSON format.

The solution was to use the DocumentExternalizer for Documents, but
a new ArrayExternalizer for Arrays. This ArrayExternalizer still
uses BSON, but it uses a subset of the BSON representation to
serialize Array objects. But, it does work well and fixes the
problem.

Quite a few new tests were added to verify that the various
operations with various parameters are indeed externalizable. The
tests don't cover all the permuations, but they do attempt to cover
the different kinds of operations with documents and arrays.

To make the Operation objects easily testable, equals and hashCode
methods were added to all the Operation subclasses. Additionally,
all of the externalizers were manually reviewed for asymmetric read
and write methods (e.g, writing an object to the ObjectOutputStream
but reading an integer from the ObjectInputStream), and several
asymmetries were found in the Externalizers for BSON value types
that ModeShape doesn't currently use, and these asymmetries were
corrected.

All unit and integration tests pass with these changes.
MODE-1703 Minor improvements

Based upon feedback, two sections of commented-out code were removed (they'd been there
for some time) and the Code.Externalizer methods were changed to use constants rather
than magic numbers for the types of the Code classes.
MODE-1693 - Added special handling to the case when transactions are not configured: a dedicated exception should be thrown
MODE-1487 Add support in the Teiid sequencer for VDB dependencies specified in its "vdb.xml"
MODE-1700 Teiid Model Sequencer Throws Error When Model Import Has Annotation
MODE-1702 Cleanup Corrupted Teiid Sequencer VDB Test Data
Removed corrupted zip files from test data. Removed ignored tests that used those corrupted zip files.
Added new VDBs to test data and added tests for those new VDBs. The new vdb.xml file XSD included
VDB dependendencies and model metadata which uses DDL to define the model. Modified VDB sequencer
and model sequencer to include these new VDB manifest features. Also added tests that test these
new features. Fixed an error where the href of a model import was not being processed.
MODE-1487 Add support in the Teiid sequencer for VDB dependencies specified in its "vdb.xml"
Cleaned up debug logging to make it consistent with the rest of ModeShape.
MODE-1702 Cleanup Corrupted Teiid Sequencer VDB Test Data
Forgot to update VDB in the integration project. Also fixed a schema validation error in the VDB manifest.
MODE-1715 Corrected variable replacement
MODE-1715 Additional correction to the variable replacement logic

The logic was incorrectly replacing blank values with null values. All works well now.
Fixed JavaDoc in JcrNodeTypeManager to no longer say registration can't update node types.
Updated release notes for 3.0.1.Final
Updated release script to better handle patch releases