Deprecate Paho component and disable related flaky test on CI

[apupier]

Description

there were no new release since 2020 of the Java client, last non-regulatory commit was in 2022
Disbale the related flaky tests CAMEL-23484

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[davsclaus]

oh that was too quick on my end. We should deprecate camel-paho, but keep the v5 as we need a dedicated MQTT client for camel.

Not sure if https://mosquitto.org/ they offer a client as there is a company that is active there

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[apupier]

Not sure if https://mosquitto.org/ they offer a client as there is a company that is active there

they are not providing a java client

seems the only active Java client is HiveMQ https://github.com/hivemq/hivemq-mqtt-client

[davsclaus]

https://github.com/hivemq/hivemq-mqtt-client

okay so lets create a JIRA about that, and see what it takes to make a new camel-hivemq component as replacement for camel-mqtt.

[apupier]

okay so lets create a JIRA about that, and see what it takes to make a new camel-hivemq component as replacement for camel-mqtt.

created https://issues.apache.org/jira/browse/CAMEL-23503

and updated PR to deprecate only the camel-paho which is based on mqtt3 protocol

[github-actions]

🧪 CI tested the following changed modules:

• catalog/camel-catalog
• components/camel-paho
• docs
• dsl/camel-endpointdsl

✅ POM dependency changes: targeted tests included

Modules affected by dependency changes (4)

• :camel-catalog
• :camel-endpointdsl
• :camel-paho
• :docs

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• components/camel-paho: 4 test(s) disabled on GitHub Actions

All tested modules (11 modules)

• Camel :: Catalog :: Camel Catalog
• Camel :: Docs
• Camel :: Endpoint DSL
• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container
• Camel :: Paho (deprecated)
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin

---

⚙️ View full build and test results