[
https://issues.apache.org/jira/browse/CAMEL-25030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121905#comment-18121905
]
Claus Ibsen commented on CAMEL-25030:
-------------------------------------
No, PR 27104 shouldn't be backported to 4.22.x. In fact it can't be:
- The component isn't on 4.22.x. camel-hivemq was added on main on 2026-09-02
(CAMEL-23503, #26006). It is new in 4.23.0, and origin/camel-4.22.x has no
components/camel-hivemq. The only MQTT components there are camel-paho and
camel-paho-mqtt5.
- It's a new feature, not a fix. CAMEL-25030 is a "New Feature" that adds a
mqttVersion option for MQTT 3.1.1. LTS branches only take CVE and critical bug
fixes.
- The change is large. It adds a new endpoint option, a client-adapter refactor
of the endpoint, consumer and producer, and regenerated catalog and DSL files.
That's 35 files changed.
Users on 4.22.x who need MQTT 3.1.1 can keep using camel-paho.
> Supply a MQTT 3.1.1 component
> ------------------------------
>
> Key: CAMEL-25030
> URL: https://issues.apache.org/jira/browse/CAMEL-25030
> Project: Camel
> Issue Type: New Feature
> Components: camel-mqtt
> Affects Versions: 4.22.1
> Reporter: Thomas Strauß
> Priority: Major
> Fix For: 4.23.0
>
>
> camel-paho supplies currently the mqtt3.1.1 implementation but is deprecated
> in 4.22-LTS. Since other MQTT implementations only support mqtt 5+, camel
> looses connectivity to the mqtt3.1.1 standard.
> mqtt.org still supports mqtt3.1.1 as a living release and actually suggests
> it for wide compatibility. Many non-mqtt brokers support only 3.1.1 as an
> industry standard alternative to the proprietary protocol. In my usecase this
> is nats.io, but others can be found.
> Using a proprietary protocol means to enforce interface partners to use the
> proprietary library and also enforces possible client updates when the
> technology is updated. Using an industry standard on your external interfaces
> links you to the industry standard life-cycle which is an entirely different
> thing.
> Long story short: The camel stack should offer a new implementation on
> mqtt3.1.1 to keep connected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
