Sébastien Deleuze

I would really like have completableFuture support in lettuce!

Let's discuss next week if we introduce an API (in `RuntimeHints`?) to configure various `native-image` parameters or not. Could be useful for end users but also for portfolio projets.

I created related spring-projects/spring-framework#29090 issue scheduled for Spring Framework 6 RC1.

> I've been thinking about this some more, and I'm starting to wonder if relying on capabilities of the native build tools' Gradle and Maven plugins is a good idea....

We have already discussed this possibility with the GraalVM team in the past which has been refused, no hope to see this happening short/middle term.

+1, on Spring Native we have seen a higher than expected amount of users just using Buildpack support without Native Build Tools configured so that seems to be a strong...

> In terms of UX, what is the signal to apply AOT processing + native? gradle bootBuildImage -Pnative=true? gradle bootBuildNativeImage? My guess is that users want to have the option...

Invoking `./mvnw native:build` will not build the JAR used as input, resulting to a `Execution default-cli of goal org.graalvm.buildtools:native-maven-plugin:0.9.13:build failed: Cannot invoke "java.io.File.exists()" because "artifactFile" is null` on a fresh...

[Jersey is not yet supported](https://docs.spring.io/spring-native/docs/current/reference/htmlsingle/#support).

See related https://github.com/oracle/graal/issues/808 closed issue.