Galder Zamarreño

Looking into the test failures.

> I agree with @zakkak . I wish we did not have to install GraalVM on our build machines. today we do not. we are building the native image using...

I have pushed an update to rework a few aspects and remove baggage from previous experiments. Here are the highlights: * Generating native image configuration is produced by JVM mode...

@marko-bekhta Is there already a Quarkus version that includes the fix you did for https://github.com/hibernate/hibernate-orm/pull/7865? If so maybe @yanxuehe can try and see what he sees now?

I've replicated it, looking into it.

I guess this fixes this right? ``` [INFO] --- quarkus-maven-plugin:999-SNAPSHOT:build (default) @ getting-started-reactive --- [WARNING] [io.quarkus.deployment.configuration] Configuration property 'quarkus.package.vineflower.enabled' has been deprecated and replaced by: [quarkus.package.decompiler.enabled] [WARNING] [io.quarkus.config] Unrecognized configuration...

I've reproduced it locally, looking into it.

The fix you need is `implementation("io.quarkiverse.amazonservices:quarkus-amazon-sqs:2.+")`. That dependency cannot be test only because there is opentelemetry API in the runtime classpath that depends on that.

We recently had an issue with the AWS v1 SDK, see https://github.com/quarkusio/quarkus/issues/39548. The relevant comment here would be https://github.com/quarkusio/quarkus/issues/39548#issuecomment-2032066278. It seems that support for native compilation on AWS v1 SDK...

Thanks for the info Chris. Indeed the operator presents the same symptoms as seen in Vincent's application. We'll look into. To replicate: ``` git clone https://github.com/quarkiverse/quarkus-operator-sdk cd quarkus-operator-sdk mvn install...