Preparing to release 1.8.2 with the split stores xml fix
check metadata incorrect results, hard analysis

Fix the new admin metadata check command and did the same change
for old admin command.

1) If check metadata fails it says true or false but not the
  actual failure.
2) Check metadata sometimes incorrectly reports failure depending
   on the order in which stores are returned.
3) Check metadata will reprot success if a store is completely missing
   from one of the nodes. It does not track number of times retrieved.

With this commit the check metadata is done using a map.

For stores check
The map will be from storeName to (map from store defintion
to nodeName)

for other
The map will be from object of that key to nodename.

This map will be used for consistency check. This map will group non
matching information to groups for easier analysis. The lenght of the
value in the map will be evaluated for missing information, solving the
problem 2 and 3 listed above
[python client] Fixed reconnect in _execute_request
Merge pull request #179 from mojn/reconnect-bugfix

[python client] Fixed reconnect in _execute_request
Merge pull request #178 from arunthirupathi/checkMetadata

check metadata incorrect results, hard analysis
first commit of junit tests

first commit for junit tests.
gradle junit has 30% failure rate, still waiting stabilization