Adjustments to JerseyClientBuilder to use configuration options otherwise ignored

Please see issue #557 in the issue tracker.

The basic problem was that the DW JerseyClientBuilder didn't properly take into account a lot of the configuration options you can pass to a Client object, particularly the proxying features.  This uses code taken from ApacheHttpClient4 to process those configuration options and get them into the ClientHandler object so they'll be properly picked up.

This is my first pull request, so apologies if I did it wrong.  :)
OK, I've made the requested changes, and thanks for the advice on
TravisCI.  :)  Please let me know if you see anything else you'd like
changed.


On Fri, Jun 13, 2014 at 4:13 PM, Jochen Schalanda <notifications@github.com>
wrote:

> In
> dropwizard-client/src/main/java/io/dropwizard/client/JerseyClientBuilder.java:
>
> >  import java.util.List;
> >  import java.util.Map;
> >  import java.util.concurrent.ExecutorService;
> > +import java.util.logging.Level;
> > +import java.util.logging.Logger;
>
> Please use the SLF4J Logger
> <http://www.slf4j.org/apidocs/org/slf4j/Logger.html> like the rest of the
> Dropwizard project.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dropwizard/dropwizard/pull/558/files#r13769751>.
>