Gradle Quarkus GRPC generator from proto separately from other components

[orchestr7]

I'm working with a multi-module Gradle project consisting of:

• common
• backend
• driver

The common module is included in both other projects. I need to generate Quarkus gRPC code from proto files that will be accessible from all three modules, with Mutiny variants included.

When I try to add the Quarkus plugin to the common module to generate the code there:

plugins {
    id 'io.quarkus'
}

I'm running into dependency clashes and other conflicts. The Quarkus plugin seems to be bringing in too many opinions about the project structure.

Is there a way to just generate the gRPC code from proto files without applying the full Quarkus plugin to the common module? Perhaps using just the protobuf-gradle-plugin or some other approach that would:

1. Generate both standard gRPC and Mutiny variants
2. Make the generated code available to all modules
3. Avoid the dependency conflicts I'm seeing with the Quarkus plugin

Has anyone solved this cleanly in a multi-module Gradle setup?

[quarkus-bot[bot]]

/cc @alesj (grpc), @cescoffier (grpc), @glefloch, @quarkusio/devtools

[orchestr7]

@jmini I think you have done something like that here #27388 (comment)