* Migrate the module's code back into this project. * Fold the documentation in. * Update to current Gradle conventions. * Reformat to match styling.
23 lines
1.4 KiB
Plaintext
23 lines
1.4 KiB
Plaintext
[[modules]]
|
|
= Spring Session Modules
|
|
|
|
In Spring Session 1.x, all of the Spring Session's `SessionRepository` implementations were available within the `spring-session` artifact.
|
|
While convenient, this approach was not sustainable long-term as more features and `SessionRepository` implementations were added to the project.
|
|
|
|
With Spring Session 2.0, several modules were split off to be separate modules as well as managed repositories.
|
|
Spring Session for MongoDB was retired, but was later reactivated as a separate module.
|
|
As of Spring Session 2.6, Spring Session for MongoDB was merged back into Spring Session.
|
|
|
|
Now the situation with the various repositories and modules is as follows:
|
|
|
|
* https://github.com/spring-projects/spring-session[`spring-session` repository]
|
|
** Hosts the Spring Session Core, Spring Session for MongoDB, Spring Session for Redis, Spring Session JDBC, and Spring Session Hazelcast modules.
|
|
|
|
* https://github.com/spring-projects/spring-session-data-geode[`spring-session-data-geode` repository]
|
|
** Hosts the Spring Session Data Geode modules. Spring Session Data Geode has its own user guide, which you can find at the [https://spring.io/projects/spring-session-data-geode#learn site].
|
|
|
|
Finally, Spring Session also provides a Maven BOM ("`bill of materials`") module in order to help users with version management concerns:
|
|
|
|
* https://github.com/spring-projects/spring-session-bom[`spring-session-bom` repository]
|
|
** Hosts the Spring Session BOM module
|