The JSON serialization could still break in certain cases, as not all escape sequences were accounted for.
I updated the Reporter class to use the battle-tested StringEscapeUtils to escape the generated JSON string. We're running the plugin internally on our SonarQube instance and so far this has solved all serialization issues.
The JSON serialization could still break in certain cases, as not all escape sequences were accounted for.
I updated the
Reporter
class to use the battle-testedStringEscapeUtils
to escape the generated JSON string. We're running the plugin internally on our SonarQube instance and so far this has solved all serialization issues.