davsclaus opened a new pull request, #3260:
URL: https://github.com/apache/camel-kamelets/pull/3260

   Fixes #2890.
   
   Removes `mqtt-source` and `mqtt-sink`, the MQTT 3.1.1 Kamelets. They use 
`camel:paho`, which Camel has deprecated since 2.16. #2890 had decided to keep 
them until Camel removes the component. The Kamelets overhaul of 4.24 removes 
them now instead, as it did with the other old Kamelets (#3165, #3166, #3255).
   
   | Removed | Use instead |
   |---|---|
   | `mqtt-source` | `mqtt5-source`, with a broker that supports MQTT 5 |
   | `mqtt-sink` | `mqtt5-sink`, with a broker that supports MQTT 5 |
   
   For a broker that only speaks MQTT 3.1.1, use the `paho` component directly, 
while Camel still has it.
   
   ### What changed
   - **Kamelets:** the two `kamelets/*.kamelet.yaml`, their copies in 
`library/camel-kamelets`, their 
`docs/modules/ROOT/partials/*-description.adoc`, and the Pipe examples in 
`templates/pipes/core` and `templates/pipes/camel-k` are removed.
   - **`mqtt5-source` and `mqtt5-sink`:** their descriptions sent a broker that 
only speaks MQTT 3.1.1 to the removed Kamelets. They now say that the broker 
must support MQTT 5.
   - **`KameletPrefixSchemeEnum`:** the `mqtt` entry (`paho`) goes. `mqtt5` 
stays.
   - **Catalog tests:** the `mqtt-*` rows in `KameletsCatalogTest` and 
`remove-headers/kamelets.csv` go.
   - **Generated:** `nav.adoc`, `kamelets-index.json` and the catalog SBOM, 
which no longer lists `camel:paho`.
   
   ### Upgrade note
   This goes in #3190, under "Removed Kamelets", when the PR is merged.
   
   ### Tests
   No Citrus test used these Kamelets. The `mqtt5` Citrus tests are unchanged. 
`./mvnw clean install` from the root passes, run twice.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to