CDI issues with Gradle multi-subproject in Kotlin

[TheBroach]

Hi!
I am working on a simple blueprint-project for starting new Quarkus-Kotlin projects. I am following the Ports & Adapters design pattern and also want to follow the recommended approach from Gradle with multiple subprojects and convention plugins for sharing configurations across them. I also do not want to add Quarkus to a subproject if I do not need it, for example in the Domain subproject which should only contain pure business logic with little to no side effects.

However when applying the Quarkus Gradle plugin to several subprojects, I get an UnsatisfiedResolutionException. I have created an MCVE for you to check out which should replicate my scenario. Note that repository definitions are omitted, see the README.

If you see any potential improvements that could be made for my blueprint project, please point them out! :)

Thanks!
/John

[quarkus-bot[bot]]

/cc @Ladicek (arc), @geoand (kotlin), @glefloch, @manovotn (arc), @mkouba (arc), @quarkusio/devtools

[mschorsch]

Quarkus 3.11.3 is rather old.

Could you try using Quarkus 3.14.2, Kotlin 2.0.10 and Gradle 8.10.1?

Hint: Do not use Quarkus 3.14.3 because it has several issues with Gradle which will be fixes with Quarkus 3.14.4.

[TheBroach]

Thanks for the tip! I bumped to those versions, unfortunately the issue remains. (The example repo is updated to those versions now.)

[mschorsch]

You have to add a beans.xml in meta-inf in each module (see https://quarkus.io/guides/cdi-reference#bean_discovery).

[TheBroach]

I checked the JARs domain.jar, driven-adapters.jar and driving-adapters.jar, they all had the META-INF/jandex.idx file...

[Ladicek]

Then I guess you're using the Quarkus plugin incorrectly. It makes no sense to use the Quarkus plugin on arbitrary modules -- it should only be present in the module that assembles the final application. (This module should have a dependency on all the other modules that constitute the application.)

[TheBroach]

Hm... Couldn't there be Quarkus features that I would want to use in a module designated for other things than to assemble the whole application, such as an "infrastructure"/"driven adapter" module where I would like to use some convenient REST client or GRPC client features from Quarkus?

[Ladicek]

That is correct, and you should feel free to use Quarkus dependencies in those modules. But you don't need to use the Quarkus Gradle plugin there.

[TheBroach]

Oooh, ok... Thanks, got it working now using a separate "application" module. I will update my MCVE when I've cleaned it up a bit!

Still curious about things that are sort of related to Quarkus-Gradle-tasks, such as generating code for a GRPC client in that potential "infrastructure"/"driven adapter" module... Will continue toying around with that, can post a new question if that proves too big of a challenge as well!