Repository navigation
Split the Spring Data module by store - #9
Merged
Merged
Conversation
semantic-ddd-spring-data now holds what every Spring Data store shares and depends on the core alone. semantic-ddd-jpa becomes semantic-ddd-spring-data-jpa on top of it, and semantic-ddd-spring-data-mongodb is added beside it. The starter no longer picks a store.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Spring Data module now holds what every store shares and depends only on the core. The JPA module becomes semantic-ddd-spring-data-jpa on top of it, and a semantic-ddd-spring-data-mongodb module is added beside it, so the base classes can serve MongoDB as well as JPA. The starter no longer picks a store: a service adds the module of its own. The READMEs, the package names and the module diagrams follow the new layout.