Summary

Restructures into a multi-module Maven project with a parent POM. This follows other community Spring Data projects such as redisson and spring-data-jest.

⚠️ This will impact existing branches/PRs as it moves all files from src to spring-data-valkey/src.

Closes #37.

Features

• Moved spring-data-valkey to its own module directory
• Added parent module for consolidated dependency management and versioning (single version for all modules)
• Updated/consolidated all READMEs to avoid duplication of information
• Added a DEVELOPER guide that goes over building and testing the modules
• Added Makefile targets to simplify running examples and performance tests

Implementation

🔍 The key changes are in:

• All README.md files - The parent README is more of an introduction, child READMEs go into more technical detail
• All pom.xml files - All common dependencies and plugins, plus all versioing information, is in the parent POM
• CI actions (ci.yml and release.yml) - Simply tests or packages the parent module, which will automatically build or package all the child modules
• Newly added DEVELOPER.md - Goes over how a developer can build and test each of the modules, and other developer tasks

Note that child modules can only inherit from a single parent, so had to manually add some dependencies and plugins from spring-data-parent to spring-data-valkey.

Testing

Completed:

• spring-data-valkey and spring-boot-starter-data-valkey installation and unit tests (./mvn clean install and ./mvn clean test)
• Ran all examples and performance tests
• Tested both Makefile targets and individual execution of Maven modules
• Tested release process still includes Spring Data Valkey and starter

What's Next

Update the CI release action to automatically sign and publish artifacts to Maven.