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 2023/06/26 06:27:26 UTC
[GitHub] [camel-quarkus] jamesnetherton opened a new issue, #5014: Allow `extensions-*` module tests to be run with alternate BOMs
jamesnetherton opened a new issue, #5014:
URL: https://github.com/apache/camel-quarkus/issues/5014
### Description
Aside from the `integration-tests` & `integration-tests-jvm` modules, we also have tests scattered in a few other places:
* extensions
* extensions-core
* extensions-jvm
* testframework
Currently, it is not possible to run those tests and override the `quarkus-bom` or `camel-quarkus-bom` GAVs. It would be useful it that were possible.
--
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] Allow `extensions-*` module tests to be run with alternate BOMs [camel-quarkus]
Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on issue #5014:
URL: https://github.com/apache/camel-quarkus/issues/5014#issuecomment-5046970745
Done in https://github.com/apache/camel-quarkus/pull/8882.
--
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
Re: [I] Allow `extensions-*` module tests to be run with alternate BOMs [camel-quarkus]
Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on issue #5014:
URL: https://github.com/apache/camel-quarkus/issues/5014#issuecomment-4904036226
Revisiting this with revised approaches...
An alternative might be to move the tests out of extensions / extensions-jvm and into their respective modules under integration-tests / integration-tests-jvm. With the following caveats:
* Ignore tests under extensions-core. They can stay as-is
* Consider only for tests covering interoperability with Quarkus or non-Camel transitives
* Ignore tests that 'overlap' (i.e test similar or same things) with existing ones under integration-tests / integration-tests-jvm
--
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
Re: [I] Allow `extensions-*` module tests to be run with alternate BOMs [camel-quarkus]
Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton closed issue #5014: Allow `extensions-*` module tests to be run with alternate BOMs
URL: https://github.com/apache/camel-quarkus/issues/5014
--
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