Skip to content

fix: okhttp4 resource path rename and unpin hardcoded okhttp version#26

Open
zeitlinger wants to merge 1 commit intojack-berg:okhttp-sender-major-versionsfrom
zeitlinger:fix/okhttp4-resource-path
Open

fix: okhttp4 resource path rename and unpin hardcoded okhttp version#26
zeitlinger wants to merge 1 commit intojack-berg:okhttp-sender-major-versionsfrom
zeitlinger:fix/okhttp4-resource-path

Conversation

@zeitlinger
Copy link
Copy Markdown

Follow-up fixes for open-telemetry#8086.

Changes

  • exporters/sender/okhttp4/build.gradle.kts: generateMainResources was missing an eachFile path rename. Without it, version.properties lands at io/opentelemetry/exporter/sender/okhttp/internal/version.properties inside the okhttp4 jar (wrong package path). The jar listing in the PR confirms both paths are present. Added the same eachFile rename that generateMainSources and generateTestSources already have.

  • exporters/otlp/testing-internal/build.gradle.kts: Reverts the explicit okhttp:5.3.2 pin — dependencyManagement already manages the project-wide okhttp5 version, so this hardcode will drift on version bumps.

…ersion

- generateMainResources was missing eachFile path rename, causing
  version.properties to land at the wrong package path in the jar
- testing-internal hardcoded okhttp 5.3.2; let dependencyManagement own it
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger zeitlinger marked this pull request as ready for review April 9, 2026 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant