Alexandre Gallice

Please do not merge. At this stage, this PR should check whether it build on CI and how to run `mvn clean verify` on perf-regression.

@jamesnetherton @ppalaga With `mvn clean verify`, we could early detect potential breakage in the `perf-regression` tool before using it during the release. How could we run those integration tests for...

Looks good to me, it's ready for review.

@lucamaf Do you still have time to work on this ? I think it's just a matter of targetting the main branch, changing to `camel-quarkus-xml-jaxp` and running `mvn clean install...

@svkcemk It's look good to me. Well done :+1: Just one more thing. It's really nice to have separate commits during review. Before merging, it would be good to rebase...

The same kind of issue happens in `FileTest.filter`: ``` org.awaitility.core.ConditionTimeoutException: org.apache.camel.quarkus.component.file.it.FileTest expected "Hello2" but was "" within 10 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164) at org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:645) at org.apache.camel.quarkus.component.file.it.FileTest.filter(FileTest.java:170) ```...

It seems to still be there after 2.8.0-M1. At least, we have seen it once in a Windows build: ``` org.awaitility.core.ConditionTimeoutException: org.apache.camel.quarkus.component.file.it.FileTest expected "Hello2" but was "" within 10 seconds....

We had another occurence of this in https://github.com/apache/camel-quarkus/runs/5790386191?check_suite_focus=true : ``` 2022-04-01T15:54:17.3802934Z org.awaitility.core.ConditionTimeoutException: org.apache.camel.quarkus.component.file.it.FileTest expected "Hello2" but was "" within 10 seconds. 2022-04-01T15:54:17.3803866Z at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167) 2022-04-01T15:54:17.3804696Z at org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86) 2022-04-01T15:54:17.3805481Z at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)...

Caught another occurence in integration-tests-alternative-jdk, this time in `FileTest.idempotent`: ``` 2022-05-05T17:20:42.1752186Z org.awaitility.core.ConditionTimeoutException: org.apache.camel.quarkus.component.file.it.FileTest expected "Hello1" but was "" within 10 seconds. 2022-05-05T17:20:42.1752848Z at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167) 2022-05-05T17:20:42.1760375Z at org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86) 2022-05-05T17:20:42.1761109Z at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)...

At this stage, we've experienced this flakiness once on alternative-platform, few times on alternative-jdks and never on regular itests. And as of now, the failing test is either idempotent or...