Orphan classes in java-support

[Brent Putman]

> I spent more time back at HTTPResource land this morning, and I think I see
> what is going on.  Brent will confirm, but AIUI both the HTTPResource and
> the HTTMetadataResolver have/will have HttpClient objects as constructor
> parameters.  HttpClientBuilder (and HttpClientSupport) or their successors
> will almost certainly have a job to do to create these specialized versions
> of HttpClient.  I suspect that this will all be buried in Spring
> configuration, whereas in V2 the parsers summoned the builder up on the fly.

Yes.  And amongst other reasons, that's because Apache HttpClient is
moving to a model (so they say) where you will no longer be able to just
'new' an instance of HttpClient (e.g. DefaultHttpClient in the past). 
You must use their builder to create instances.  And theirs aren't very
Spring-friendly - they're skewing more towards a fluent-style API.  So
going forward, perhaps even more so than now, we'll need some types of
HttpClient builder/support/etc classes. (unless they totally switch
directions again...)