ArC and Vert.x: introduce InvokerFactoryBuildItem and use it in Vert.x event bus consumers

[Ladicek]

The last commit fixes #26728

[Ladicek]

Probably easiest to review each commit separately.

[cescoffier]

We need to rework the dependency on Kotlin. Main extensions should not depend on it.

[cescoffier]

Could it introduce an issue to depend on Kotlin here?

[cescoffier]

That's not great. Now everything depends on Kotlin.

[Ladicek]

It's just a tiny artifact with 3 classes and transitive dependencies on artifacts that are already present, but I agree it is not nice. I took this over from the Scheduler extension without thinking too much about it. I'll ponder over it over the weekend.

[mkouba]

I think that it's fine. It does not really bring the Kotlin sdk in (it's an optional dependency)...

[Ladicek]

Added one more commit (to be squashed if you guys like it :-) ) that moves the dependency to the quarkus-kotlin module. Probably not very nice either, but should be better than a dependency on Kotlin in the quarkus-vertx module, I guess.

[mschorsch]

Thank you @Ladicek for taking the time to improve the Kotlin support in Quarkus 👍

[Ladicek]

Rebased and added one more commit (again, to be squashed) that turns the Kotlin support into an extension which is automatically present when both quarkus-kotlin and quarkus-vertx are present (due to https://quarkus.io/guides/conditional-extension-dependencies). Seems like the best way forward to me.

[github-actions]

🙈 The PR is closed and the preview is expired.

[Ladicek]

Rebased and squashed the last 3 commits.

[manovotn]

Went over ArC parts and those LGTM

[mkouba]

Looks good!

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit ea2c6a4.

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

⚠️ There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit ea2c6a4.

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

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase.sseStream - History

• Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase Expecting size of: [] to be greater than or equal to 2 but was 0 within 10 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase 
Expecting size of:
  []
to be greater than or equal to 2 but was 0 within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)

[geoand]

Very cool!

So I assume we should start using invokers wherever possible?

[Ladicek]

That sounds reasonable, but at the same time, there are occasions where custom bytecode generation is more straightforward. I also vaguely recall that I couldn't use invokers in RESTEasy Reactive, for some reason.