Fix Jaeger/Zipkin tracing orbit bundles

[manodyaSenevirathne]

Problem

APIM gateway startup fails due to OSGi wiring issues for Zipkin reporter packages (zipkin2.reporter.Reporter / zipkin2.reporter.BytesEncoder) when used via Jaeger/Brave and OpenTelemetry exporters.

Changes

Jaeger orbit: widen zipkin2.reporter import range and bump orbit version to 1.8.0.wso2v2.
Zipkin sender orbit: embed/export zipkin2.reporter and bump orbit version to 3.5.1.wso2v2 so dependent OTEL exporters can resolve reporter classes.

Summary by CodeRabbit

• New Features
  • Added support for Jaeger distributed tracing framework (JDK21 compatible) with full OpenTracing integration
  • Added support for Zipkin distributed tracing with OkHttp3 sender capability

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 85d6905f-9a65-4a6e-9f70-db8c7bdda4f9

📥 Commits

Reviewing files that changed from the base of the PR and between 049c212 and 4da5423.

📒 Files selected for processing (2)

• jaeger-client-jdk21/1.8.0.wso2v2/pom.xml
• zipkin-sender-okhttp3/3.5.1.wso2v2/pom.xml

---

Walkthrough

Two new Maven OSGi bundle configurations were added for Jaeger client JDK21 and Zipkin sender OKHttp3, each defining packaging specifications, dependency declarations, package exports, import constraints, and distribution endpoints as WSO2 orbit artifacts.

Changes

Cohort / File(s)	Summary
OSGi Bundle Definitions jaeger-client-jdk21/1.8.0.wso2v2/pom.xml, zipkin-sender-okhttp3/3.5.1.wso2v2/pom.xml	New Maven POM files configuring OSGi bundles with explicit package exports (io.jaegertracing.*, io.opentracing.*, brave.* for Jaeger; zipkin2.reporter* for Zipkin), import package constraints with version ranges, embedded dependencies, and WSO2 orbit distribution management.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Two bundles bound for OSGi's embrace,
Jaeger and Zipkin find their place,
With exports clean and imports tight,
Maven's magic shines so bright! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provided is minimal and deviates significantly from the required template structure. While it mentions the problem and changes, it lacks most required sections including Purpose, Goals, Approach, User stories, Release notes, Documentation, Training, Certification, Marketing, Automation tests, Security checks, and other template sections.	Expand the description to follow the template structure more closely by adding sections for Goals, Approach, Release notes, Documentation, Security checks, Test environment, and other applicable template sections to provide complete context for reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Fix Jaeger/Zipkin tracing orbit bundles' clearly and concisely summarizes the main change of updating two OSGi bundle configurations to resolve tracing framework integration issues.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}