Ability to generate gRPC descriptor set

[edeandrea]

Ability to generate gRPC descriptor sets.

@cescoffier please take a look. In the code gen I needed a way to get access to the project root directory so that the user could specify an output directory relative to that. I modified the Maven & Gradle plugins to provide that info into the generation. I also added a bunch of tests to both plugins.

Fixes #36897

[edeandrea]

The majority of the 50 changed files are new integration tests that I added.

[github-actions]

🙈 The PR is closed and the preview is expired.

[cescoffier]

There is a * import to fix. The rest looks good. I've asked Aleš and Alexei to have a look for the gRPPC protoc part and maven/gradle part.

[quarkus-bot]

Failing Jobs - Building 43b7e08

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	Gradle Tests - JDK 11
✖	Gradle Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

✖ io.quarkus.gradle.CustomManifestArgumentsTest.shouldContainsSpecificManifestProperty line 37 - More details - Source on GitHub

java.lang.AssertionError: 

Expecting actual not to be null

[edeandrea]

@gsmet I'm not sure whats up with that Gradle integration test. I see it failing on other PRs as well, so I'm not sure I did anything here that would cause that failure.

[johannesctrl]

Hi, I appreciate the new feature of generating the descriptor file a lot because I would like to use this for WireMock. However, I am not able to generate it. While ...

• using Maven
• using Quarkus version 3.6.0.CR1
• adding quarkus.generate-code.grpc.descriptor-set.generate=true to my application.properties
• defining the goals "build", "generate-code" and "generate-code-tests"

I am getting the warning that the key cannot be found:
"[WARNING] [io.quarkus.config] Unrecognized configuration key "quarkus.generate-code.grpc.descriptor-set.generate" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo"

[edeandrea]

Hi @johannesctrl have you tried it with 3.6.0 (the released version)?

Using it with Wiremock is exactly why I did this PR in the first place :)

[edeandrea]

@johannesctrl I just added that to the grpc-locations project within the Quarkus superheroes and I see that it was generated:

You can customize the name & location of the file by using the quarkus.generate-code.grpc.descriptor-set.output-dir and quarkus.generate-code.grpc.descriptor-set.name properties:

quarkus:
  generate-code:
    grpc:
      descriptor-set:
        generate: true
        output-dir: .
        name: locationservice-v1.dsc

[johannesctrl]

Thank you so much for checking! :) Yes, I already tried the 3.6.0 version and also using the name and location properties. Maybe it's something else in my settings ... I'm gonna check all my settings again, I guess 😄

[edeandrea]

You can look in the the grpc-locations project within the Quarkus superheroes (pom.xml, etc) to see how it was configured.

All I did was clone that and run

./mvnw clean package -DskipTests -Dquarkus.generate-code.grpc.descriptor-set.generate=true -Dquarkus.generate-code.grpc.descriptor-set.output-dir=. -Dquarkus.generate-code.grpc.descriptor-set.name=locationservice-v1.dsc

You could also add the properties to src/main/resources/application.yml (this project uses yaml config).