Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: googlielmo <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-427-brooklyn-server@git.apache.org>
In-Reply-To: <git-pr-427-brooklyn-server@git.apache.org>
Subject: [GitHub] brooklyn-server issue #427: Use servicemix bundle for okio
Content-Type: text/plain
Message-Id: <20161111094819.146C9E01F4@git1-us-west.apache.org>
Date: Fri, 11 Nov 2016 09:48:18 +0000 (UTC)
archived-at: Fri, 11 Nov 2016 09:48:21 -0000

Github user googlielmo commented on the issue:

    https://github.com/apache/brooklyn-server/pull/427
  
    @aledsage cc: @neykov @andreaturli 
    I played a little with this and my conclusion is that since `jclouds-http` imports both `okhttp` and `okio`, having restricted the dependency `okhttp` -> `okio` will force the more specific version of `okio` to be wired to it.
    That said, I'm worried that `jclouds-http` doesn't seem to specify a version for `okhttp`, which might cause it to wire to `okhttp` 3 (maybe?). Better report that to the jclouds team.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---