slackapi / slackapi/java-slack-sdk

Update okhttp to 5.x

Open
#1,500 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triage-skip dependencies project:slack-api-client project:slack-app-backend
Dominant language
Java
Stars
602
Forks
232
Avg merge
4d 9h
Merged PRs (30d)
7

Description

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 BanDuplicateClasses due 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
  • bolt (Bolt for Java)
  • bolt-{sub modules} (Bolt for Java - optional modules)
  • slack-api-client (Slack API Clients)
  • slack-api-model (Slack API Data Models)
  • slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
  • slack-app-backend (The primitive layer of Bolt for Java)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the dependency declarations in pom.xml, including the Kotlin version noted in its comment, and identify the modules covered by the request. Review the OkHttp 5.x artifact split and update scope, then run the project's validation checks to confirm BanDuplicateClasses no longer reports conflicts across the listed Java and Kotlin components.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kotlin
Domain
build-system
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.