Vojin Jovanovic

What is a definitive reference? We will document this better in the upcoming releases, but first, we need to revisit the defaults. I feel this one should be included by...

I wish I had a good answer. We will be improving this feature for JDK 23. Until then the best I can say is that this is the list of...

Thank you very much for reporting the issue! We will look into it and see why it happens.

This requires moving FileSystemProviders to runtime. I tried making this change and many things failed because of the initialization strategy we use. I would wait for the new initialization strategy...

Would setting up the `-H:-AddAllFileSystemProviders` at image build help as a temporary workaround?

This looks like a message from older versions of GraalVM. Have you tried with the latest dev build, or with the GraalVM for JDK 21 with a flag `--strict-image-heap`?

I think we need to add the option `--strict-image-heap` to make it work. I could not use the reproducer as it uses Spring snapshots. What is the right combination of...

Hope this can be a workaround for everyone until this issue is fixed as a part of https://github.com/oracle/graal/issues/7488.

Have you tried to reduce that list of initialized classes when the `--strict-image-heap` is used?

We will try to move security classes to run-time init in the future, but it is uncertain whether it will be possible. Until then this looks like a good solution.