verify that primary stream is ordered as expected
open primary stream in same thread as the multithreading might cause
issues with streams, e.g. using Hibernate
fixed unit test: stream was not ordered as expected
resolved checkstyle issues (as far as it made sense)
Update master
Merge pull request #8 from sfussenegger/patch-1

Update README for numeric sorting
be more explicit in exception message (see
https://github.com/molindo/scrutineer/commit/c606e9a4d8a9e2272766cbc088cd89eb76abe131#commitcomment-1455448)
Merge pull request #7 from molindo/verifier

IdAndVersionStreamVerifier improvements
Upgrade Scrutineer to use ES 0.19.10 client library.  No, this isn't the latest, yes I realise that..
Ensure that Scrutineer reports an identifiable 'node.name' when joining the ES cluster so that it's easier to identify in the ES cluster logs.

Pull out a NodeFactory class that constructs the Node object based on the expected properties needing to be set.

Pull out the Command Line object to a top-level class.
Change the log4j configuration to use some more standard logging patterns which at least emit some local time element.

It's not easy to take the time-since-jvm-start in any meaningful way, at least for us.  Ensure we also leave behind a log file for posterity.
Add the logs directory to be ignored.
Introduce a Function that formats the version value when being output, with the default merely passing it through natively.

This will allow introduction of formatting options for cases where the version value is a timestamp, so we can output the values later on in ISO8601 format.
Optimize imports, somehow my IntelliJ settings have been nuked.
Introduce a TimestampFormatter that prints the raw value along with a timezone sensitive formatted string for easy human readable eyeballing of the date/time.
When provided on the commandline, version values are now output with human readable timestamp values for easier triage on any inconsistencies.
Upgrade the Maven AppAssembler plugin to a later version that supports a Wildcard classpath option to make dropping in other JDBC drivers simpler for others.
Issue #10 Use a default Java Heap of 256Mb instead of the default 64, because our default batch size ends up being bigger than this heap can support.

Modified the README to include a section on memory use and how to override the value should it be necessary.
[maven-release-plugin] prepare release scrutineer-1.0.5
[maven-release-plugin] prepare for next development iteration