remove constructors compatibility

[just_a_fish]

* This change may call many compatibility problems. * Many libaray depend on snakeyyaml(such as spring,apollo and so on). If they are not match, it will encoutered a no method exception. * It will push many project and code to updrade to the new version and its very high risk to the users. * problems link: https://github.com/apolloconfig/apollo/issues/4960 https://stackoverflow.com/questions/75870282/is-snakeyaml-2-0-added-in-the-new-spring-boot-versions

‌

‌

[Andrey Somov]

What is your proposal ?

[just_a_fish]

Maybe it should keep the constructors until some time.

[Andrey Somov]

Why to keep ? what do you expect to get ?

For you information:

• it was done 2 releases ago
• the constructors were removed because release 2.0 was NOT backwards compatible anyway
• please check the rest of the changes
• how long should it be kept ? It was deprecated for many years

‌

[just_a_fish]

• Thanks your repsonse.
• Maybe because springboot3 use snakeyaml 2.2 and springboot2 use snakeyyaml 1.28. If annother libaray update snakeyaml, the users must upgrade the springboot version or other library. And it is a heavy job for users.
• I think what you do is right and reasonable. What confused me is just beacuse snakeyaml is used by so many projects and some of them is so heavy to update.
• And i found one compatible method is using java reflection to construct the object.

‌

[Andrey Somov]

Sorry, I do not get your message

[Andrey Somov]

Do you have any questions left ?
Can we close the issue ?

‌

[just_a_fish]

You can close the issue.