[GitHub] [camel-quarkus] jamesnetherton opened a new issue, #4570: Split infinispan testing into separate modules for the quarkus and camel managed clients

["jamesnetherton (via GitHub)" <gi...@apache.org>]

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

   Maintaining the Infinispan tests is becoming a bit painful due to having tests for both the Quarkus Infinispan client and the client created by the camel component all co-located.
   
   It'd be better to do like we have with AWS and test these different scenarios in isolation.


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

[GitHub] [camel-quarkus] jamesnetherton closed issue #4570: Split infinispan testing into separate modules for the quarkus and camel managed clients

["jamesnetherton (via GitHub)" <gi...@apache.org>]

jamesnetherton closed issue #4570: Split infinispan testing into separate modules for the quarkus and camel managed clients
URL: https://github.com/apache/camel-quarkus/issues/4570


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