Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As GraalVM native image switched the default to initialize mostly everything to runtime initialization by default (apart from known safe classes https://www.graalvm.org/22.1/reference-manual/native-image/ClassInitialization/#automatic-initialization-of-safe-classes), we don’t have to cater for the default in the driver. The rest is taking care of by the recent netty versions.
In Quarkus we must defer Netty SSL explicitly to runtime (
return new RuntimeInitializedPackageBuildItem("io.netty.handler.ssl“)
), as Quarkus insists of Built-Time-Initialization by default and our SSL config will than trigger the above at a point in time in which the Quarkus built-in substitions are not in place yet.