Hi I think its good to deprecate as we are on the way for all those major upgrades as part of the SB4 effort and so on.
We can surely remove these before 5.x as that is many years out in the wild. And Camel has always removed old deprecated components from time to time. Especially when there is another component that is replacing it to use - in fact if we were able to do this in a faster way, then such work would sometimes just be in the same component, and end user would need to migrate. Nothing is set in stone forever. On Thu, Mar 5, 2026 at 9:10 AM Pasquale Congiusti < [email protected]> wrote: > Hi team, > in the past I've worked to introduce new components and provide a better > consistency for telemetry [1] and mdc logging [2]. I think these components > are now mature enough and we should evaluate the deprecation of the older > components that these new ones are planning to replace. In particular I > have these 2 issues: > > https://issues.apache.org/jira/browse/CAMEL-22479 > https://issues.apache.org/jira/browse/CAMEL-22477 > > If there is no objection, we can deprecate them, reminding the user to use > the newer components instead. I advocate not to remove before any major > upgrade though (5.x), unless force majeure such as vulnerabilities or > problems we won't be able to manage easily during the rest of 4.x > development cycles. Happy to read any feedback around this task. > > Thanks for the collaboration, > Pasquale. > > [1] https://camel.apache.org/components/4.18.x/others/telemetry.html > [2] https://camel.apache.org/components/4.18.x/others/mdc.html > -- Claus Ibsen
