You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2021/03/11 07:59:00 UTC

[jira] [Created] (CAMEL-16336) Make CustomSlackHttpClient compatible with okhttp 3.x

James Netherton created CAMEL-16336:
---------------------------------------

             Summary: Make CustomSlackHttpClient compatible with okhttp 3.x
                 Key: CAMEL-16336
                 URL: https://issues.apache.org/jira/browse/CAMEL-16336
             Project: Camel
          Issue Type: Improvement
          Components: camel-slack
    Affects Versions: 3.9.0
            Reporter: James Netherton


See discussion in Zulip about CustomSlackHttpClient here:

https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/CustomSlackHttpClient

The slack-api-client is bound to okhttp 4.x and CustomSlackHttpClient seems to be an effort to make the component bin compatible with okhttp client 3.x. But the RequestBody.create method signature used is referencing the 4.x APIs instead of 3.x.

Perhaps we should override and force okhttp 3.x in the component pom.xml and do the necessary bin compat tweaks in CustomSlackHttpClient? I'm no expert on okhttp or the slack-api-client so not sure if this can work reliably.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)