Closed sincebyte closed 1 year ago
What version do you want to use? You can refer to the upgrade guide on the official website to determine the compatibility.
I just want to confirm did seata client's version need match to the server's?
e.g. I use seata-server 1.6.1 and io.seata:seata-core:jar:1.5.2
for the springboot app ,even throuth I use io.seata:seata-spring-boot-starter:jar:1.6.1
. Case the depencies
[INFO] | | \- com.alibaba.cloud:spring-cloud-starter-alibaba-seata:jar:2021.0.5.0:compile
[INFO] | | \- io.seata:seata-spring-boot-starter:jar:1.6.1:compile
[INFO] | | +- io.seata:seata-spring-autoconfigure-client:jar:1.6.1:compile
[INFO] | | | \- io.seata:seata-spring-autoconfigure-core:jar:1.6.1:compile
[INFO] | | \- io.seata:seata-all:jar:1.6.1:compile
[INFO] | | +- org.apache.dubbo.extensions:dubbo-filter-seata:jar:1.0.0:compile
[INFO] | | | +- io.seata:seata-core:jar:1.5.2:compile
[INFO] | | | | +- io.seata:seata-common:jar:1.5.2:compile
[INFO] | | | | \- io.seata:seata-discovery-core:jar:1.5.2:compile
[INFO] | | | | \- io.seata:seata-config-core:jar:1.5.2:compile
And I think there do not have a clear describe regard to seata component and their respective configration. Yea, you guys wrote a documentation but it just describe every option's mean. I'm still confused about where this configuration should be placed,and when they will be loaded and use. I mean evey configuration, the every one.
This is a bug discovered because the Maven transitive dependency in Dubbo caused the use of a lower version of seata-core
. This has been fixed in the latest version. You can manually exclude seata-core
and introduce a dependency with the same version as that of seata-spring-boot-starter.
这是一个发现的bug,因为dubbo 侧maven传递依赖导致了使用低版本的seata-core
,这个在新版本已经修复。你可以手动排除seata-core
,引入与seata-spring-boot-starter 相同版本的依赖。
Did the versions of seata-server
and io.seata:seata-core:jar
must euqal?
Or It's actually unknown.
Or It's very complicated, it depends on the situation.
如问题