Use latest Apache HTTP client (v4.3.5)
Merge pull request #44 from spotify/rohan/apache

Use latest Apache HTTP client (v4.3.5)
TravisCI: Move commands into .travis.sh script

Rather than having a bunch of shell commands stuffed into yaml.
TravisCI: Test Unix socket support

Rather than just running all tests against an HTTP endpoint, run two
workers in parallel -- with one using HTTP and the other using Unix
sockets.
Merge pull request #45 from spotify/rohan/travis

TravisCI: Test Unix socket support
README: Better layout of build status badge
Fix test image to be all lowercase for Docker v1.3

Docker v1.3.0 requires all image names to be entirely lowercase.
Merge pull request #46 from spotify/rohan/travis

Fix test image to be all lowercase for Docker v1.3
Don't use SocketFactoryService for Unix sockets

The SocketFactoryService has a bug wherein the first lookup sometimes
returns null. Work around this by using the UnixSocketFactory directly.
Merge pull request #47 from spotify/rohan/sf

Don't use SocketFactoryService for Unix sockets
[maven-release-plugin] prepare release v2.5.0
[maven-release-plugin] prepare for next development iteration
Upgrade to Jersey 2.x

This lets us use the async support in Jersey rather and get rid of our
interruptible client handlers.

It's also a step on the way to proper TLS support.
Shade/relocate Jersey & its deps to fix conflicts

Jersey and its dependencies (Jackson, JAX-RS, etc.) are now included into
the docker-client JAR and relocated to the com.spotify.docker.client.shaded
package.

This prevents conflicts in projects that use Jersey 1.x. Any project should
be able to use docker-client as a dependency, regardless of which version
of Jersey it uses.

Tested with Helios (Dropwizard 0.7 + Jersey 1.18) and there were no issues
with conflicting Jersey versions after this change.
Merge pull request #51 from spotify/rohan/ssl

Upgrade to Jersey 2.x
Fix bug where dates are several days in the future

Docker returns timestamps with nanosecond precision (e.g.
2014-10-17T21:22:56.949763914Z), but the Date object only supports
milliseconds. Creating a Date from the nanosecond timestamp results
in the date being set to several days after what date should be.
This class converts the timestamp from nanoseconds to milliseconds
by removing the last six digits of the timestamp, so we can generate
a Date with the correct value (albeit with less precision).

Note: a more complete solution would be to introduce a custom date
type which can store the nanosecond value in an additional field, so
users can access the complete value. Or just use Java 8 which has
date objects with nanosecond support.