[MRESOLVER-249] Update Hazelcast to 5.1.1 #164
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
Update Hazelcast from 5.0.2 to latest 5.1.1. This is really not a game changes, as Hazelcast 5.x is binary compatible, so end users may choose which version to use for real.
michael-o
requested changes
Apr 12, 2022
Member
michael-o
left a comment
michael-o
left a comment
There was a problem hiding this comment.
This one is missing: https://maven.apache.org/resolver/maven-resolver-named-locks-hazelcast/index.html
michael-o
approved these changes
Apr 12, 2022
Member
michael-o
left a comment
michael-o
left a comment
There was a problem hiding this comment.
Please add the HZ versoin to the commit title and the JIRA issue as well.
cstamas
changed the title
|
Resolve #950 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Update Hazelcast from 5.0.2 to latest 5.1.1. This is really
not a game changer, as Hazelcast 5.x is API compatible, so
end users may choose which version to use for real at runtime.
https://issues.apache.org/jira/browse/MRESOLVER-249