Brian Clozel 38019d2249 Allow static registration of RuntimeHints ... Prior to this commit, we could only contribute `RuntimeHints` through two mechanisms: * `AotContributingBeanFactoryPostProcessor`, consdering the entire `BeanFactory` and designed for contributing both code and hints. * `AotContributingBeanPostProcessor`, consdering beans one by one, but also designed for contributing both code and hints. There are cases where libraries and applications want to contribute `RuntimeHints` only, in a more static fashion: a dependency being present, or a piece of infrastructure being considered by the application context are good enough signals to contribute hints about resources or reflection. This commit adds the `RuntimeHintsRegistrar` contract for these cases. Implementations can be declared as `spring.factories` and they will be processed as soon as they're detected on the classpath. They can also be declared with `@ImportRuntimeHints` and they will be processed if the annotated bean definition is considered in the application context. This annotation should be mainly used on configuration classes and on bean methods. ``` @Configuration @ImportRuntimeHints(CustomRuntimeHintsRegistrar.class) public class MyConfiguration { @Bean @ImportRuntimeHints(OtherRuntimeHintsRegistrar.class) public MyBean myBean() { //... } } ``` Closes gh-28160		2022-04-14 13:06:43 +02:00
..
src	Allow static registration of RuntimeHints	2022-04-14 13:06:43 +02:00
spring-core.gradle	Implement GraalVM native JSON configuration generation	2022-03-16 16:15:58 +01:00