Update to SmallRye Fault Tolerance 5.1.0 and add Vert.x integration

[Ladicek]

Fixes #17080

[Ladicek]

Draft because

• I want to let CI run in my fork;
• I need to add some tests.

[famod]

Is this also going to fix the Java 16 issues?

[Ladicek]

Indeed this will fix the Java 16 issues. I totally forgot to revert that commit -- thanks for reminder!

[Ladicek]

CI passed in my fork.

[Ladicek]

@michalszynkiewicz could you please review the SmallRyeFaultToleranceProcessor change? (Sorry, can't think of anyone else, I don't really know who wrote the FT extension originally :-) )

[famod]

Have you tried running the tcks tests locally with Java 16? Thing is CI runs them only with Java 11.
What I could do alternatively is to create a branch from yours here in the main repo and run the EA job for it...

[Ladicek]

I did run the TCK locally with Java 16, but only on the SmallRye Fault Tolerance repo, that is, with Weld. Let me do that again with Quarkus.

[Ladicek]

This is what I just did locally, on commit 490ca98, that is, on the branch corresponding to this PR:

find . -type d -name target -print0 | xargs -0 rm -rf
mvn clean install -Dquickly
export JAVA_HOME=/usr/lib/jvm/java-16-openjdk-amd64
cd tcks/microprofile-fault-tolerance/
mvn clean verify -Dtcks

And the result is Tests run: 435, Failures: 0, Errors: 0, Skipped: 0.

In other words, the MP FT TCK passes on Java 16 just fine :-)

[cescoffier]

Should we merge this one?

@famod I believe @Ladicek did the Java 16 tests.

[Ladicek]

Merging would certainly be nice :-)

[Ladicek]

I mean, @cescoffier if you could take a look at what I did to the Vert.x extension, that would be even nicer! I couldn't think of a better place where to put the integration dependency. An unfortunate side effect is that the quarkus-vertx artifact now transitively brings exactly 1 new dependency, smallrye-fault-tolerance-vertx, but that thing only includes like 4 classes and weights 6 KBs, so should be fine.

[famod]

Thanks for checking the FT TCK on Java 16!

[cescoffier]

LGTM, the new dependency is acceptable as it rather small. We can revisit this later if need be.