Best way to develop reusable quarkus libraries (in gradle)

[toniwe]

Hi everyone! My goal is to create libraries (in a multi-module gradle project) that include certain Quarkus functionalities and reuse them in a lot of microservices (all of which are quarkus apps, jvm and native). I would also like to reuse them inside Quarkus-Extensions.

My question goes in a similar direction as #27587 . However, I also intend to use certain features, that currently only seem to be available using the "io.quarkus" Plugin, which is made for building Quarkus Apps, not libraries.

The needed features for my libraries include:

• Providing Quarkus Beans / @ApplicationScoped classes
• Writing Quarkus-Tests for those
• Generating and using GRPC (especially Mutiny variants) classes as well as AVRO classes

My current solution uses the quarkus Plugin, disables some of the tasks to only output a jar to publish later, which I consider a bad workaround.

Regarding GRPC, I've already seen this discussion #48155 so at least for GRPC this seems technically possible without the quarkus plugin.

Is there a definitive / "best practice" way to achieve all of that in Quarkus? Thanks!

[quarkus-bot[bot]]

/cc @glefloch, @quarkusio/devtools