Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/427
Looks good. Agree with @googlielmo's thinking that `okhttp` should restrict
the version even for `jclouds-http`, but worth a check.
What I'd like to see are fixes for upstream projects - servicemix okhttp
2.2.0, 3.4+, jclouds-http before considering this done deal.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
