Juergen Hoeller

Related enhancements in 6.0: #1215, #19846

Closing this for the time being since we have no immediate need for closer alignment with the ServiceLoader mechanism. From a core framework perspective, `SpringFactoriesLoader` is a rather specific mechanism...

On a related note, after #28414, the `ConstructorOrFactoryMethodResolver` class re-implementing constructor resolution at this point refers to the `@Autowired` annotation directly, creating a package cycle between `beans.factory.aot` and `beans.factory.annotation`. This...

I'm narrowing the scope of this ticket for our immediate purposes in 6.0, namely merging AOT constructor and factory method resolution into `ConstructorResolver` in the `beans.factory.support` package. This moves related...

Our strategic alignment with the module system has been in competition with our AOT and GraalVM native image efforts in 6.0, so we unfortunately had no chance to experiment with...

As per our 6.0 wrap-up discussions and my recent comment on #18079, the module system has not been a priority for 6.0 (for reasons explained in that comment). Not least...

@dreis2211 We decided to move forward with the Introspector bypass for 6.0 still, in time for Boot 3.0 RC1 next week: #29320 The implementation that is about to be pushed...

@dreis2211 see my comment on #29320 - we could potentially backport an optional variant of this to 5.3.x. Let's continue the conversation over there, we've been hijacking this thread enough...

Virtual thread support is effectively a Spring Framework 6.1 topic, assuming that Project Loom may go out of preview for JDK 21 in September next year. For the time being,...

The stacktrace above suggests that a CGLIB proxy is being created from a class in that package. If that is unavoidable, the module needs to be declared as open: https://stackoverflow.com/questions/46482364/what-is-an-open-module-in-java-9-and-how-do-i-use-it...