CMS7-6784 compilation on java 7

CMS7-6704: prepare release jcrdiff-1.01.02

CMS7-6607 only try to order children if they are orderable

CMS7-6404: As a Developer, I want to be able to read and edit my patches for the new updater console features in an easy format

CMS7-6404: As a Developer, I want to be able to read and edit my patches for the new updater console features in an easy format 
  - Applied the second review comment from Frank

CMS7-6430 bump project pom to latest tagged version

CMS7-6404: As a Developer, I want to be able to read and edit my patches for the new updater console features in an easy format 
  - Fixed the updates problem
  - Added tests for that
  - 1 down one to go (the paths problem)

CMS7-6380: changed scope of easymock dependencies to 'test'

Also moved all dependencies to the dependencyManagement section of the root pom, and defined all versions as properties. Reused properties from the project pom where possible.

CMS7-6339 add ability to filter items from patch

CMS7-6338 add getters for source and target fields; return null instead of UOE

CMS7-6043: prepare for next development iteration

CMS7-5997: allow root node to be removed

CMS7-5825: prepare for next development iteration

CMS7-5825: use jcrdiff for the parent project name, provide names for modules

CMS7-5825: remove obsolete distribution management section

CMS7-5688: improve output format

CMS7-5688: turn JcrDiffException into a checked exception

The new PatchLog interface allows custom logging during application of patches.

CMS7-5688: simplify move sort algorithm

fix unit tests using in-mem tree.

CMS7-5688: use attic when deleting items

When a deleted item is replaced by an inserted item at the same location, move
the deleted item to the attic to prevent same-name-sibling problems.

When an item is no longer found when the patch is processed, only throw a
JcrDiffException, as that's expected when a patch cannot be applied.

CMS7-5688: match properties more accurately

- ignore hippo:paths
  we don't depend on uuid's, and they will be updated anyway.  They only mess
  up the hash code calculation.
- set subtree hash for properties too
  since those are used in the top-down; they should be there
- ignore the child position when comparing
- when finding the best match, use all ancestors to determine whether a match is good
 

CMS7-5688: support property move

CMS7-5688: type info on nodes and properties

- store type (primary + mixins) on nodes
  a type is not required, in which case the jcr implementation will fall back to nt:unstructured
  the in-memory implementation does not do any validation, but can store this type information
- type info on properties is stored as a string value

CMS7-5688: support single and multi-valued properties

HGGE-17: children element has been renamed to child

CMS7-5688: add copyright headers