[ISSUE #12342] Resolve the Hessian package conflict issue. #12449
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
KomachiSion
approved these changes
Aug 5, 2024
MoritzArena
pushed a commit
to MoritzArena/nacos
that referenced
this pull request
Aug 7, 2024
This was referenced Aug 19, 2024
KomachiSion
added a commit
to KomachiSion/nacos
that referenced
this pull request
Aug 28, 2024
This reverts commit 5d8d81a.
KomachiSion
added a commit
that referenced
this pull request
Aug 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What is the purpose of the change
fixes #11963
Resolve the Hessian package conflict issue.
Brief changelog
Replaced the jraft-core Hessian dependency version
3.3.6and the original Nacos project dependency oncom.caucho:hessian:4.0.63withcom.alipay.sofa:hessian:4.0.4.Verifying this change
We have been using this solution in our production environment since version 2.2.x, and it has been validated across versions 2.3.3 and 2.4.0.1. Throughout the use of this solution for service startup, as a configuration center, and as a registration center, no issues have been encountered.