Deprecate Jaeger propagator

[Kielek]

Package

OpenTelemetry.Extensions.Propagators

Is your feature request related to a problem?

Links:

open-telemetry/opentelemetry-specification#4827
https://www.jaegertracing.io/sdk-migration/#propagation-format

What is the expected behavior?

Jeager propagator API is marked as oblsolete both in Propagators package.
Also legacy API in OpenTelemetry package should updates the messages.

Which alternative solutions or features have you considered?

N/A

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[neeraj542]

Hi @Kielek,

I'd like to work on this issue. I've reviewed the requirements:

• Mark Jaeger propagator APIs as obsolete in OpenTelemetry.Extensions.Propagators using [Obsolete] attributes
• Update legacy API messages in the main OpenTelemetry package

I understand this aligns with:

• The OpenTelemetry specification change (Deprecate Jaeger propagator opentelemetry-specification#4827)
• Jaeger's migration guide recommending OTLP/W3C Trace Context propagator

I plan to:

1. Locate all Jaeger propagator classes/methods in the Propagators package
2. Add appropriate [Obsolete] attributes with clear deprecation messages
3. Search and update legacy API messages in the main package
4. Will ensure the consistency across the codebase

Could you assign this to me? I'm ready to start.
Thanks!

[Kielek]

@neeraj542, looking forward for the PR.

[neeraj542]

Thanks @Kielek, I’m working on this and will open a PR very soon