Remove dependencies on Jaeger from opentelemetry-collector-contrib #6408
Labels
area/otel
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
Today we have circular dependencies between Jaeger and OTEL contrib repos. We want to move towards one way Jaeger->OTEL/contrib dependency model. This requires refactoring of how Jaeger internal code is organized and moving some of the code out to OTEL/contrib.
This is a relatively large undertaking that needs to happen piecemeal.
Here are all the current OTEL/contrib -> Jaeger dependencies (Dec-2024):
The text was updated successfully, but these errors were encountered: