Handle avro generator in gradle

[glefloch]

I saw that avro code generator was integrated in the main branch.
This add support in the gradle plugin.

[geoand]

Seems like you need to:

Error: Dependencies in integration-tests/gradle/pom.xml are outdated!
Error: Run update-dependencies.sh in integration-tests/gradle and add the modified pom.xml file to your commit.
Error: Process completed with exit code 1.

:)

[glefloch]

right! I tried to do it manually but it didn't work :) I will run the script.

[glefloch]

@famod I don't understand what is going on.. I ran the script on my machine (both new version working on mac os, and current version in a container) and the pom does not change but ci is complaining.. do you have an idea?

[famod]

@glefloch I'll have a look!

[famod]

I added git diff to the workflow step (something I should have done a while ago):

diff --git a/integration-tests/gradle/pom.xml b/integration-tests/gradle/pom.xml
index bfd5a86c8e..e5ab1bcb4a 100644
--- a/integration-tests/gradle/pom.xml
+++ b/integration-tests/gradle/pom.xml
@@ -94,21 +94,11 @@
             <artifactId>quarkus-resteasy</artifactId>
             <version>${project.version}</version>
         </dependency>
-        <dependency>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-resteasy-jsonb</artifactId>
-            <version>${project.version}</version>
-        </dependency>
         <dependency>
             <groupId>io.quarkus</groupId>
             <artifactId>quarkus-test-devtools</artifactId>
             <version>${project.version}</version>
         </dependency>
-        <dependency>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-vertx</artifactId>
-            <version>${project.version}</version>
-        </dependency>
         <dependency>
             <groupId>io.quarkus</groupId>
             <artifactId>quarkus-arc-deployment</artifactId>
@@ -200,32 +190,6 @@
                 </exclusion>
             </exclusions>
         </dependency>
-        <dependency>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-resteasy-jsonb-deployment</artifactId>
-            <version>${project.version}</version>
-            <type>pom</type>
-            <scope>test</scope>
-            <exclusions>
-                <exclusion>
-                    <groupId>*</groupId>
-                    <artifactId>*</artifactId>
-                </exclusion>
-            </exclusions>
-        </dependency>
-        <dependency>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-vertx-deployment</artifactId>
-            <version>${project.version}</version>
-            <type>pom</type>
-            <scope>test</scope>
-            <exclusions>
-                <exclusion>
-                    <groupId>*</groupId>
-                    <artifactId>*</artifactId>
-                </exclusion>
-            </exclusions>
-        </dependency>
         <!-- END update-dependencies.sh -->
     </dependencies>

So in CI, the script is removing vert.x and jsonb... Does that make any sense?

[famod]

Hm, looking at what you added/changed in this PR, I have to say I understand why the script is removing those dependencies: neither of the two deps was added to any of the build*.gradle files.

[glefloch]

Well I think it make sense. I tried reverting all modification in the pom running the script again but, I have the same result. I will drop those new dependency manually

[famod]

...and now I can also replicate the behavior locally. First the script didn't change anything for me locally either because I called it via integration-tests/gradle/update-dependencies.sh but that will only work after #15823 was merged!
Currently you have to cd integration-tests/gradle && ./update-dependencies.sh and on Mac you are out of luck.

[glefloch]

I'm running it in integration-tests/gradle

[famod]

Then you should see the same effect as in CI.

[michalszynkiewicz]

it's really bad that we need this list. Can we access classpath resources in here?