Update snakeyaml to version 2.0 in api/build.gradle.kts #1047
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
I was getting error java.lang.NoSuchMethodError: 'void org.yaml.snakeyaml.LoaderOptions.setCodePointLimit(int)' using snakeyaml 2.0 in my plugin. I learned that the Velocity core contains the snakeyaml version 1.33 library. I suggest replacing the version with 2.0 because of the large number of vulnerabilities in the older version
|
I have the same issue. It would be great to update to version 2.0 or even 2.2! |
|
SnakeYAML 2.x is a major API breakage. The best we can do is version 1.33. |
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.
I was getting error java.lang.NoSuchMethodError: 'void org.yaml.snakeyaml.LoaderOptions.setCodePointLimit(int)' using snakeyaml 2.0 in my plugin. I learned that the Velocity core contains the snakeyaml version 1.33 library. I suggest replacing the version with 2.0 because of the large number of vulnerabilities in the older version