Removing Spring AI BOM #541
Merged
Conversation
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
I ran another test:
Remove Spring AI BOM folder from .m2:
rm -rf ~/.m2/repository/org/springframework/ai/spring-ai-bomReload Maven project:
2.1. with Redis OM Spring v0.9.8:
Directory and contents are recreated
2.2. with a new snapshot of Redis OM Spring without Spring AI BOM:
Directory and contents are not recreated.
Turns out that even though Maven won't download the actual dependencies (and that's why nothing shows in the dependency tree), it will still import the POM file of the BOM. To avoid this from happening, I simply removed the BOM and managed the versions of Spring AI optional dependencies manually.