[GitHub] [camel-quarkus] ppalaga opened a new issue #3156: Simplify the dependency management of examples using QuarkusProcessExecutor

[GitBox <gi...@apache.org>]

ppalaga opened a new issue #3156:
URL: https://github.com/apache/camel-quarkus/issues/3156


   Once the BOMs used in examples will get parametrized ( https://github.com/apache/camel-quarkus/issues/3123 ) there will be no `camel-quarkus.version` available in their poms. This is an issue for the few examples using `QuarkusProcessExecutor` from `camel-quarkus-integration-test-support` that is managed in `camel-quarkus-bom-test`. We'd have to keep and maintain `camel-quarkus.version` in the example poms because of this. 
   
   Several options come to my mind:
   
   A. Put `QuarkusProcessExecutor` and all code it depends on into a new module with a nicer name (e.g. `camel-quarkus-test-utils` ) and manage it in our application BOM.
   B. Move `QuarkusProcessExecutor` to `quarkus-junit-5` or some similar module managed in `quarkus-bom`. Hard to say how well our `AvailablePortFinder` could be made portable/replaced?
   C. Copy `QuarkusProcessExecutor.java` and all necessary code to the individual examples
   
   Any opinions?
   
   I think I prefer A. 


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