spring-aot-smoke-tests VS taming-build-time-initialization

There’s an extensive set of smoke tests in this repo that suggest something fundamental can’t be broken. https://github.com/spring-projects/spring-aot-smoke-tests If you have the time, please file an issue with Boot including a bit more details (failure output etc.) so that we can have a look.

You can have a look to https://github.com/spring-projects/spring-aot-smoke-tests that we use that test various use cases and related https://ci.spring.io/teams/spring-aot-smoke-tests/pipelines/spring-aot-smoke-tests-1.0.x CI test results.

We have developed a GraalVM feature that allows to precompute at build time the value of static fields without having to use build-time initialization of classes, so you get some of the benefits in term of build time code removal without the compatibility drawback. Build time class initialization is IMO (and this advice is shared by more and more people including in the GraalVM core team) is the wrong solution to a true problem, and Spring collaborate very closely with GraalVM team and other frameworks to solve this in upcoming GraalVM versions, see https://github.com/graalvm/taming-build-time-initialization for more technical information.