[Q/A][Java SDK (Component)] Dubbo 3.x is not compatible with Spring Boot 2.1.x

[marmot-z]

Pre-check

• I am sure that all the content I provide is in English.

Apache Dubbo Component

Java SDK (apache/dubbo)

Details

In a commit in dubbo 3.x, after upgrading snakeyaml from 1.x to 2.x, the following exception will occur after starting spring boot starter 2.1.x:

java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.Constructor: method <init>()V not found
at org.springframework.boot.env.OriginTrackedYamlLoader$OriginTrackingConstructor.<init>(OriginTrackedYamlLoader.java:82)
at org.springframework.boot.env.OriginTrackedYamlLoader$OriginTrackingConstructor.<init>(OriginTrackedYamlLoader.java:82)
at org.springframework.boot.env.OriginTrackedYamlLoader.createYaml(OriginTrackedYamlLoader.java:64)
at org.springframework.beans.factory.config.YamlProcessor.process(YamlProcessor.java:132)
at org.springframework.boot.env.OriginTrackedYamlLoader.load(OriginTrackedYamlLoader.java:75)
at org.springframework.boot.env.YamlPropertySourceLoader.load(YamlPropertySourceLoader.java:50)
....

The reason is that some obsolete methods were removed in snakeyaml 2.x, which caused spring boot to fail to load the corresponding method when it started. This issue also mentioned it.

The solution I can think of is to upgrade the spring boot version to 3.0.x to ensure that the snakeyaml versions used by dubbo and spring boot are compatible. However, upgrading the spring boot version has a wide range of impacts. I would like to ask if there are other solutions besides this? 🙏🙏🙏

Code of Conduct

• I agree to follow this project's Code of Conduct

[AlbumenJ]

This is the problem with snakeyaml. You can specify your self snakeyaml version. Dubbo do not strongly depend on it.

[marmot-z]

If the snakeyaml version used by dubbo conflicts with other frameworks (such as Spring Boot), dubbo's config center feature (such as conditional routing) may be abnormal because this function relies on snakeyaml to parse the yaml configuration.

[AlbumenJ]

#15106 (comment)