ppalaga commented on issue #413: URL: https://github.com/apache/camel-quarkus/issues/413#issuecomment-642031530
Now after a couple of Camel Quarkus upgrades in the Platform and after @galderz has detected quite a few issues through our tests there, I'd like to update my standpoint as follows: * Upgrades and maintenance of our tests in the platform is not an issue with the existing tooling. `mvn validate -Pregen-camel -N` regenerates the tests from scratch, so that new tests come and stale tests disappear. It is fast and reliable. Ad hoc fixes can be (or indeed are) done in the pom.xml template: https://github.com/quarkusio/quarkus-platform/blob/master/src/rpkg-templates/run-tests-module-pom.xml#L31-L41 * Having all/nearly all our tests in the platform is a good thing. They help to uncover real issues, typically the ones caused by different dependency versions on the platform. Different dependency versions on the platform is a reality that will hardly change. There are two main sources of it: (1) quarkus-bom is imported before our BOM and (2) other 3rd party BOMs, such as Kogito BOM are imported before our BOM on the platform. Thus dependencies managed in all those 3rd party BOMs get a higher precedence that the ones managed by us. Given the above I am against bothering with creating any reduced set of tests for the platform and I vote for closing this issue. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
