You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "jamesnetherton (via GitHub)" <gi...@apache.org> on 2026/01/07 16:29:37 UTC

[I] Rationalize master extension integration testing [camel-quarkus]

jamesnetherton opened a new issue, #8114:
URL: https://github.com/apache/camel-quarkus/issues/8114

   ### Description
   
   Not sure why we have integration tests for `master` & `master-file`.
   
   The only difference seems to be the `master` test manually configures the `FileLockClusterService`, whereas with `master-file`, it's done via the `file-cluster-service` extension.
   
   I don't see the need to test both scenarios. The preferred way is to always use the `-cluster-service` extensions. So we can drop `master` and build up a suite of `master-*` test modules to test the various cluster services.


-- 
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: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Rationalize master extension integration testing [camel-quarkus]

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton closed issue #8114: Rationalize master extension integration testing
URL: https://github.com/apache/camel-quarkus/issues/8114


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org