bugfix: fix ClassNotFoundException caused when server starts when using Eureka #5179
Conversation
This file contains 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
bugfix: fix issue#5174 , when seata.registry.type is eureka, ClassNotFoundException is reported after seata-server startup
|
|
Codecov Report
@@ Coverage Diff @@
## develop #5179 +/- ##
==========================================
Coverage ? 48.45%
Complexity ? 4135
==========================================
Files ? 743
Lines ? 26517
Branches ? 3294
==========================================
Hits ? 12848
Misses ? 12270
Partials ? 1399 |
xingfudeshi
changed the title
funky-eyes
added
type: bug
|
@xssdpgy thanks for your contribution. |
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.
bugfix: fix issue#5174 , when seata.registry.type is eureka, ClassNotFoundException is reported after seata-server startup
Ⅰ. Describe what this PR did
bugfix: fix issue#5174 , when seata.registry.type is eureka, ClassNotFoundException is reported after seata-server startup
Ⅱ. Does this pull request fix one issue?
fixes #5174
Ⅲ. Why don't you add test cases (unit test/integration test)?
When seata.registry.type is eureka, you can update pom.xml , then start seata-server for verify.
Ⅳ. Describe how to verify it
update pom.xml ,then start seata-server for verify it
Ⅴ. Special notes for reviews