This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Investigate usage of module information at runtime #53
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a modulithic application is run, we could optimize the bootstrap in case the developer indicates which module they'd like to use to only eagerly initialize that mark all beans not included in the module set to be run to be marked as lazy.
Related: spring-projects/spring-framework#22559
The text was updated successfully, but these errors were encountered: