Sharding startup failed after upgrading the snake yml component to version 2.0

[sushuliang113]

sharding version：

org.apache.shardingsphere
shardingsphere-jdbc-core
5.3.2

snakeYaml version：

org.yaml
snakeyaml
2.0

Caused by: java.lang.NoSuchMethodError: org.yaml.snakeyaml.representer.Representer: method ()V not found
at org.apache.shardingsphere.infra.util.yaml.representer.ShardingSphereYamlRepresenter.(ShardingSphereYamlRepresenter.java:42) ~[shardingsphere-infra-util-5.3.2.jar:5.3.2]
at org.apache.shardingsphere.infra.util.yaml.YamlEngine.marshal(YamlEngine.java:113) ~[shardingsphere-infra-util-5.3.2.jar:5.3.2]
at org.apache.shardingsphere.mode.metadata.persist.service.config.global.PropertiesPersistService.persist(PropertiesPersistService.java:45) ~[shardingsphere-mode-core-5.3.2.jar:5.3.2]
at org.apache.shardingsphere.mode.metadata.persist.service.config.global.PropertiesPersistService.conditionalPersist(PropertiesPersistService.java:39) ~[shardingsphere-mode-core-5.3.2.jar:5.3.2]
at org.apache.shardingsphere.mode.metadata.persist.MetaDataPersistService.persistConfigurations(MetaDataPersistService.java:86) ~[shardingsphere-mode-core-5.3.2.jar:5.3.2]
at org.apache.shardingsphere.mode.manager.standalone.StandaloneContextManagerBuilder.persistConfigurations(StandaloneContextManagerBuilder.java:61) ~[shardingsphere-standalone-mode-core-5.3.2

[RaigorJiang]

ShardingSphere now uses snakeyaml 1.3.3, there may be compatibility problem with different versions.

[linghengqian]

• @sushuliang113 Hey, I've flagged this issue, which is Markup SpringBoot users need to specify SnakeYAML version in Github Wiki #21476 and Upgrade snakeyaml to 2.0 #24636 .

• Due to the fact that modifying to SnakeYaml 2.0 functions would compromise the compatibility of all current versions of the Spring Framework, I tend to wait for the Spring Team to make the changes first.

[zhchhawks]

• @sushuliang113 Hey, I've flagged this issue, which is Markup SpringBoot users need to specify SnakeYAML version in Github Wiki #21476 and Upgrade snakeyaml to 2.0 #24636 .
• Due to the fact that modifying to SnakeYaml 2.0 functions would compromise the compatibility of all current versions of the Spring Framework, I tend to wait for the Spring Team to make the changes first.

I am using 4.1.1, will this version support snakeyaml 2.0?

[linghengqian]

• @sushuliang113 Hey, I've flagged this issue, which is Markup SpringBoot users need to specify SnakeYAML version in Github Wiki #21476 and Upgrade snakeyaml to 2.0 #24636 .
• Due to the fact that modifying to SnakeYaml 2.0 functions would compromise the compatibility of all current versions of the Spring Framework, I tend to wait for the Spring Team to make the changes first.

I am using 4.1.1, will this version support snakeyaml 2.0?

• Considering the API changes in SnakeYAML in the last 2 years, I don't think this is possible.

[hsld9527]

• @sushuliang113 Hey, I've flagged this issue, which is Markup SpringBoot users need to specify SnakeYAML version in Github Wiki #21476 and Upgrade snakeyaml to 2.0 #24636 .
• Due to the fact that modifying to SnakeYaml 2.0 functions would compromise the compatibility of all current versions of the Spring Framework, I tend to wait for the Spring Team to make the changes first.

SpringBoot 2.7.10 alreadey supports SnakeYaml 2.0, but I see there is no Sharding 4.x to support SnakeYaml 2.0, and the problem still exists

[linghengqian]

• @sushuliang113 Hey, I've flagged this issue, which is Markup SpringBoot users need to specify SnakeYAML version in Github Wiki #21476 and Upgrade snakeyaml to 2.0 #24636 .
• Due to the fact that modifying to SnakeYaml 2.0 functions would compromise the compatibility of all current versions of the Spring Framework, I tend to wait for the Spring Team to make the changes first.

SpringBoot 2.7.10 alreadey supports SnakeYaml 2.0, but I see there is no Sharding 4.x to support SnakeYaml 2.0, and the problem still exists

• Considering that it is impossible to commit back to the ShardingSphere 4.x branch, I think this is an impossible thing.

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.