Sébastien Deleuze

Duplicated of #28638 that I just made a bit more generic.

Hey, Spring Framework committer here. I am not sure that would be as simple as adding those 2 additional annotations since: - Spring use case is leveraging meta annotations -...

Spring Framework is unlikely to change this code path which could introduce regressions on JVM side. I would suggest to add related hints on Spring Data side (and maybe check...

@snicoll Could you please share with Christoph if that's possible (I am not sure it is)?

This is a known side effect of current JSR 305 support, the Java compiler generates warning on annotation with enum values when not present in the classpath while it is...

Thanks for the insight, I am going to give it a try.

Seems to work as expected based on my tests: - No side effects detected by NullAway when building Spring Framework - Kotlin null-safety seems to be effective like before the...

I had sadly to [revert the related commit](https://github.com/spring-projects/spring-framework/commit/d6e9562aebcd520b5edf1edd59b25768562efbdd) as, as observed by @jhoeller, IntelliJ IDEA is not able to recognize `@Nullable` semantics with that change. @cpovirk Let's maybe discuss that...

Suspending functions should not be used with `@Bean` and for factory methods, Spring Framework 6.2+ is going to throw an exception for such use case (including when AOT is used)....

Very interested on this since we would like to migrate Spring as well. I will give it a try on Spring side and provide a feedback.