Deprecation warning for --initialize-at-build-time

[piotr-yuxuan]

--initialize-at-build-time without arguments has been deprecated when not using --diagnostics-mode. With GraalVM 22.0.0 --initialize-at-build-time will only work with --diagnostics-mode for debugging purposes.
The reason for deprecation is that --initalize-at-build-time does not compose, i.e., a single library can make assumptions that the whole classpath can be safely initialized at build time; that assumption is often incorrect.

[FieryCod]

@piotr-yuxuan Could you please elaborate what action is required? The information you have posted is already known by the members of the organization and we doing our best to educate people to not use initialize-at-build-time without an argument.

[piotr-yuxuan]

Aw, sorry haha, indeed the message is really scarse! I forgot to add more context. I've noticed that some of the libraries tested here use the flag --initialize-at-build-time with no arguments, and I think some (tedious, time-consuming) manual action might be needed to update the examples – happy to help if need be.

[piotr-yuxuan]

Kudos for the extremeley fast response time, and sorry again for the very abrupt first message :-)

[FieryCod]

@piotr-yuxuan don't sorry :D. I can't speak for other members, but yet I don't know what to do with this project. For me, it's a great testing field for new libraries I want to integrate with GraalVM. Proving something might work with GraalVM is always the first step. What I do next is I do take the example to graal-config repository and I'm trying to provide a configuration that might be shared with the other users (see https://github.com/clj-easy/graal-config)