[I] Rethink how we exclude / skip tests in the Quarkus Platform [camel-quarkus]

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

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

   ### Description
   
   If we encounter test issues in the Quarkus Platform, typically this is resolved by modifying the Camel member configuration and adding a `<skip>` option. E.g like here:
   
   https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L397-L400
   
   Unless all of the tests for a specific extension are broken, then `<skip>` is perhaps not the best strategy.
   
   Maybe it would be better to configure things so that any tests that do still work can continue to be executed. E.g via the `jvmIncludes` or `jvmExcludes` config. There is equivalent config for native (`nativeExcludes` etc).


-- 
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] Rethink how we exclude / skip tests in the Quarkus Platform [camel-quarkus]

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

ppalaga commented on issue #5586:
URL: https://github.com/apache/camel-quarkus/issues/5586#issuecomment-1840872223

   +1, thanks for suggesting it, I did not know those options even exist. There is even an example in the Platform POM: https://github.com/quarkusio/quarkus-platform/blob/4419cececb8ff48e475e122ac83162b9b4692905/pom.xml#L244-L250


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