oscerd commented on issue #2890: URL: https://github.com/apache/camel-kamelets/issues/2890#issuecomment-5887978417
**Decision: option 3 — keep as-is until Camel actually removes these components.** The evidence behind it, from the 4.22.0 refresh above: `paho` has been deprecated since **2.16.0** and `splunk` since **2.13.0**, and neither has been removed across many major versions. `json-patch` has no replacement to migrate to at all. Nothing in the catalog is forced, and the two alternatives both cost more than they buy right now — option 2 changes protocol behaviour for `mqtt-*` users while largely duplicating the existing `mqtt5-*` Kamelets, and option 1 needs a deprecation convention the catalog does not have. Leaving this open deliberately, as the body always intended — it is the tracker that keeps the three deprecations from being forgotten. The trigger to revisit is upstream removal, not a date. On the signalling gap I raised: noted and **not** being acted on now. Inventing a `Deprecated` support level or a `camel.apache.org/kamelet.deprecated` annotation is a catalog-wide contract change that tooling reads, so it wants its own proposal and review rather than arriving as a side effect of this follow-up. Worth doing before a removal actually lands, not because of one. No code change; recording the decision so the next person reading this does not re-derive it. --- _Claude Code on behalf of Andrea Cosentino_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
