Alex Katlein

On it!

@gsmet `quarkus-hibernate-orm` pulls in `quarkus-agroal` which leads to `quarkus-agroal-deployment` being picked up by the Gradle plugin. However, none of the reactive DB extensions specifies an exclusion for `quarkus-agroal` in their...

As far as I understand those are exclusions in the Maven project model, not in the Quarkus extension model. Shouldn't artifacts excluded by an extension be specified under `excluded-artifacts` in...

The Gradle plugin doesn't know about the pom. It only reads the `quarkus-extension.yaml` file and looks at previously configured dependencies (e.g. from a pom) when building the deployment classpath. So...

One of the main changes I made to the Gradle plugin is to recursively pull in all extensions' deployment modules to also get those where one extension or module may...

I added these exclusions to `quarkus-reactive-datasource`: ```xml io.quarkus:quarkus-agroal io.quarkus:quarkus-agroal-deployment io.quarkus:quarkus-narayana-jta io.quarkus:quarkus-narayana-jta-deployment io.smallrye:smallrye-context-propagation-jta ``` This made the reproducer start without issue. However, this breaks all extensions relying on JDBC datasources (e.g....

@aloubyansky I wrote to you on Zulip about some topics where I need to increase my understanding, which (I think) has no place in this issue.

After talking to @aloubyansky a bit I realized that's what was missing from the Gradle plugin. Will try to find out how we can best handle those exclusions.

@aloubyansky @gsmet @janek64 One bug fix coming up :) The reproducer of this issue is a new integration test case for the Gradle plugin ;)

@shohruh-genius Yes, because you are pulling in `io.quarkus:quarkus-jdbc-postgresql`. However, the point of this issue is that we must be able to run reactive Hibernate without having to pull in a...