jamesnetherton opened a new issue, #9311: URL: https://github.com/apache/camel-quarkus/issues/9311
### Bug description Setting `quarkus.camel.cli.enabled=false` does not disable the CLI connector. When the option is `false`, the `cli-connector` extension does not register its `CliConnectorFactory` bean. Camel then falls back to discovering its default (enabled) factory from the classpath via `META-INF/services/org/apache/camel/cli-connector-factory`, since core includes `META-INF/services/org/apache/camel/*` for service discovery. The result is that the connector is still created and started. `CliConnectorDisabledTest` only verifies that no `CliConnectorFactory` is present in the registry, so it passes regardless. The `cli-connector-factory` service should be excluded from discovery, and the test should assert that no `CliConnectorFactory` context plugin or `CliConnector` service is present on the `CamelContext`. -- 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]
