Support wildcard for cluster server
Fixed broken test
Server now also allows 0.0.0.0 to be specified in settings
Fixes test that forgot to take into account the extra call to listeningAt()
Fixed broken test
Merge remote-tracking branch 'rickard/wildcardcluster' into wildcardcluster
Fixed broken test
remove all uses of getHostName()
refactor SelectorStrategy generics
Merge branch '1.9-maint' into wildcardcluster
Adds proper store directory to arbiters so they log normally
Adds extra foo into bar
Use 0.0.0.0 in arbiter instances too
Refactorings
All me URIs should be volatile, or we risk not seeing the correct value when reading it.
SPI impl is it's own class now
License header in DefaultMasterImplSPI
Merge pull request #1337 from rickardoberg/wildcardcluster

Support wildcards for cluster, backup. and HA server
Fixed unelection bug
Reduces log spam from ResourcePool

ResourcePool as used by Client was logging through a ResourcePoolMonitor that
 issued debug statements on every update of ResourcePool target values. This
 lead to needless statements as most of the time the logged values are the same.
 This commit fixes that to issue the statement only when the value changes.

Adds dependency on Mockito for testing.
Fixes potential race with duplicate votes from a particular instance

If an election times out, is cancelled and retried, it is possible for
 an instance to respond twice *after* the cancellation if its message
 is delayed for some reason. This can lead to both votes being counted,
 the required vote count reached earlier and eventually the election
 concluding with a wrong result.
 This commit fixes this by keeping the votes in a map so the latest
 overrides the previous and keeps the count correct.
Another way to go about the same result would be to have a
 monotonically increasing election id issued by the elector. While
 more correct, it's more complicated so this solution is evaluated
 first.
There was a bug whereby an instance would expect heartbeats from itself, but there are conditions to ensure this doesn't happen. On timeout the instance will then suspect itself. This has been fixed so that an instance will never expect heartbeats from itself.
Also, other bug fixes such as not registering StateTransitionLogger twice (which gave double output in messages.log)