You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we can't test the flag -H:-InitializeJDKAtBuildTimeMigration that is planned to be introduced to GraalVM with oracle/graal#10531 because GraalVM internally registers classes for build-time or run-time registrations using the same mechanisms we do.
The idea behind the -H:-InitializeJDKAtBuildTimeMigration flag is that it will not register JDK classes for build-time initialization (which is what happens now), allowing them to be run-time initialized which is the default behavior for classes without explicit build time initialization strategy. However, in Quarkus registers everything for build-time initialization so we will need to explicitly register for run-time initialization any JDK classes no longer being registered for build time initialization when using -H:-InitializeJDKAtBuildTimeMigration.
Relates to #42682 which if implemented would possibly make this easier.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered:
Description
Currently we can't test the flag
-H:-InitializeJDKAtBuildTimeMigration
that is planned to be introduced to GraalVM with oracle/graal#10531 because GraalVM internally registers classes for build-time or run-time registrations using the same mechanisms we do.The idea behind the
-H:-InitializeJDKAtBuildTimeMigration
flag is that it will not register JDK classes for build-time initialization (which is what happens now), allowing them to be run-time initialized which is the default behavior for classes without explicit build time initialization strategy. However, in Quarkus registers everything for build-time initialization so we will need to explicitly register for run-time initialization any JDK classes no longer being registered for build time initialization when using-H:-InitializeJDKAtBuildTimeMigration
.Relates to #42682 which if implemented would possibly make this easier.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: