This PR reworks Spring Session auto-configuration to avoid extending Spring Session's configuration classes. Instead, those configuration classes are now imported and customizations are applied using dedicated (Reactive)SessionRepositoryCustomizer beans.
Comment From: wilkinsona
On hold until we're ready to move to snapshots.
Comment From: vpavic
Is there a rough estimate when the move to snapshots is expected to be unblocked?
I'm asking because a lot of Spring Session's configuration infrastructure is set up the way it currently is because of reliance of Spring Boot's auto-configuration on inheritance, and the changes proposed here would allow Spring Session to evolve its configuration infrastructure. Having in mind the RCs are scheduled in just a little over 2 weeks from now, I'm trying to get a sense of the time we'll have to explore further improvements on Spring Session side.
Comment From: wilkinsona
We're trying to figure that out at the moment. Right now, it's looking like Boot will switch to snapshots of all the Spring projects on which it depends on Thursday (6 October).
Comment From: vpavic
Thanks. If the switch (and hopefully merge of this PR) happens by the end of this week, that would be great.
Comment From: wilkinsona
Thanks, @vpavic. The changes are now in main. I polished things a little in https://github.com/spring-projects/spring-boot/commit/7e47d3bbd6aadbcf38a0f84b993f3c35f56a2c76 to remove some inner-classes that were no longer necessary.