--initialize-at-build-time added with empty value
See original GitHub issueIs there a specific reason --initialize-at-build-time
gets added every time with empty value to the native-image argument list? It comes from here
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
RuntimeClassInitialization (GraalVM SDK Java API Reference)
Registers the provided classes as eagerly initialized during image-build time. static void, initializeAtBuildTime(String... packages). Registers all classes in ...
Read more >java - How to fix "Try avoiding to initialize the class that caused ...
Basically I try to include specific classes that trigger the initialization in --initialize-at-build-time . Here's what I do. Add parameter ...
Read more >Tips for writing native applications - Quarkus
Delay class initialization Using such a construct means that a --initialize-at-run-time option will automatically be added to the native-image command line. ...
Read more >Updates on Class Initialization in GraalVM Native Image ...
tl;dr: Since GraalVM 19.0, application classes in native images are by default initialized at run time and no longer at image build time....
Read more >Native Image Build Options - GraalVM - Oracle Help Center
add root modules to resolve in addition to the initial module. <module name> can also be ALL-DEFAULT , ALL-SYSTEM , ALL-MODULE-PATH; -D<name>=<value> :...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No, the command line that is printed is the one that is actually run in order to correctly produce the native image. Removing the option would result in an incorrect/non-functional build. The option is really present in the build. What Emmanuel was alluding to is that the command line options do not completely describe what is happening in the build. But they are still needed (in this case, the argument sets the default to “build time”, and we use features to establish which classes are run time, overriding the default).
Closing. This is how it should be.