Upgrade to Quarkus CXF & Camel Quarkus 3.18.0

[jamesnetherton]

Supersedes #1397.

Quarkus CXF Release Notes: https://docs.quarkiverse.io/quarkus-cxf/dev/release-notes/3.18.0.html

[jamesnetherton]

@ppalaga I had to disable the Camel CXF SOAP tests and some QCXF tests due to this issue:

apache/camel-quarkus#6940

Not sure if it's just specific to the test suite or whether there's some wider problem. The CQ itests are passing with QCXF 3.18.0 so I am a bit confused about it.

[ppalaga]

Thanks for filing the issue, @jamesnetherton.

As far as I can see, it is caused by the fact that the generated Camel BOM does not contain the org.bouncycastle:* exclusion on org.apache.wss4j:wss4j-ws-security-common which we have in io.quarkiverse.cxf:quarkus-cxf-bom. Let me figure out why is that the case.

[ppalaga]

We should not merge like this.

[ppalaga]

The problem comes from Camel Quarkus, where the generated change in Camel Quarkus poms/bom/src/main/generated/flattened-reduced-pom.xml

https://github.com/apache/camel-quarkus/blame/9cdddfff62b1de58c2c83b638707cd9a1d7202b2/poms/bom/src/main/generated/flattened-reduced-pom.xml#L7705-L7708

was commited in Next is 3.19.0-SNAPSHOT but not before the 3.18.0 release.

To avoid blocking Platfrom 3.18.0, let's add the exclusion in the generator config.

[ppalaga]

@jamesnetherton this should fix it: jamesnetherton#1 Please feel free to squash into this PR

[jamesnetherton]

@jamesnetherton this should fix it: jamesnetherton#1 Please feel free to squash into this PR

Thanks, tests passed locally.

[jamesnetherton]

@ppalaga I think CxfWssClientTest.loggingClient is potentially flaky. If you agree, I'll disable it.

[jamesnetherton]

@ppalaga I think CxfWssClientTest.loggingClient is potentially flaky. If you agree, I'll disable it.

Took the liberty of disabling them and opened issues:

quarkiverse/quarkus-cxf#1694
quarkiverse/quarkus-cxf#1695

[quarkus-bot]

Status for workflow CI Build

This is the status report for running CI Build on commit ca91626.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[gsmet]

Thanks!