Fix invalid XML characters in Surefire reports - #3408
Draft
kush2439p wants to merge 5 commits into
Draft
Conversation
Fixes apache#3399 Sanitize invalid XML 1.0 characters in Surefire reports while preserving valid supplementary Unicode characters and streamed UTF-8 output. Add focused regression coverage for report attributes, text output, CDATA, malformed UTF-8, and chunk boundaries.
Correct the source file location for apache#3399.
Remove the unchanged upstream test before replacing it with the regression coverage for apache#3399.
…t/java/org/apache/maven/plugin/surefire/report/StatelessXmlReporterTest.java Place the regression test at the existing module path for apache#3399.
Remove the accidental root-level source copy after placing the implementation in its module path.
This file contains hidden or 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
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.
Fixes #3399
What changed
Validation
The full reactor test compile was not reliable in this Windows/JDK 25 environment because of a reactor classpath/forked compiler issue; the focused reporter suite passed.
Apache checklist