Repository navigation
Update okhttp to 5.x #1500
Description
Activity
Yes, It should do the trick, but since its a major update and even though the changelog doesn't mention major breaking changes (other than the packaging), I'd rather do it the clean way if possible 😉
👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.
Hey team! Any update or timeline to share with us for the switch to
okhttp 5.x?
We are using your SDK in our project, and because ofokhttp 4.xwe are stuck in an old version ofmockwebserver(fromokhttp)...Thanks for your work 🙏
Same issue as above. okhttp v5 added support for graalvm. Please update to v5
https://square.github.io/okhttp/changelogs/changelog/This breaks for us too. Please update okHttp to 5.x
Hello, do you have any updates regarding this issue?
I'd request that this slack sdk use the JDK 11 HTTP client instead of okhttp.
Reacted by Louis Melchior@zimeg do you need some help to do that ? As @kurtostfeld pointed out, using a builtin HTTP client would be the best approach to avoid this class of problem to happen again.
Do you want us to throw some AI (like Claude Code) to it to do the refactoring?
Reacted by Eden ZimbelmanI wanted to add a little more detail: I'm working on a large Java project with lots of dependencies; the slack API is one of many. the slack API depends on okhttp which depends on the Kotlin runtime, and we have different transitive dependencies on different versions of the Kotlin runtime which causes problems in our application at runtime.
It would be ideal if the slack api used the JDK built-in http client which would reduce conflicting transitive dependencies problems. Thank you for the consideration 👍
@zimeg any news here?
Hi,
The recent OkHttp 5.x release has split the artifact into platform-specific packages (okhttp-jvm and okhttp-android). This causes issues on our projects as we can't update their okhttp dependency without breaking validation rules like
BanDuplicateClassesdue to this change of artifact id.With this update Okhttp have updated Kotlin to v2, so the Kotlin dependency will require to be updated to 2.x as well. Based on comment in pom this shouldn't be an issue.
Could you please update the OkHttp dependency to 5.x (okhttp-jvm) to avoid these conflicts?
Thanks for your consideration!
Category