Legacy XML reports should preserve new line characters in message attributes

[gtach2o]

Hello!

After switching test execution from using gradle with junit platform to console launcher I noticed that
value of message attribute in JUnit xml report loosing new line characters.
e.g.
Using gradle xml :

<error message="line 1&#10; line 2&#10; line 3&#10;"...

Using Console launcher xml:

<error message="
line 1
line 2
line 3
"

Steps to reproduce

1. Run tests using gradle with junit platform. Throw multiline exception in test.
2. Run tests using console launcher, throw multiline exception in test.

Context

org.junit.platform:junit-platform-console-standalone:1.11.3
org.junit.jupiter:junit-jupiter-engine:5.11.3
JRE 23

As I understand console launcher uses new open/xml report generator and gradle platform launcher uses legacy report generator, right?

[marcphilipp]

@gtach2o I'm not sure what you mean. In your example, there are newline characters in the attribute value. While Gradle seems to replace \n using 
, the Console Launcher includes them as-is. This is well-formed XML. Does it cause any issues downstream?

[gtach2o]

@gtach2o I'm not sure what you mean. In your example, there are newline characters in the attribute value. While Gradle seems to replace \n using 
, the Console Launcher includes them as-is. This is well-formed XML. Does it cause any issues downstream?

Well, that xml is processed by some other services and message value extracted with javax.xml.bind.annotation.XmlAttribute and stored in DB, to be later shown on html dashboard.
There is no problem with tests executed with gradle and their message is displayed correctly in the browser, with newlines. The message from tests executed with the console launcher does not displayed with line breaks. It's just one long string because there is no \n in the original value.

While Gradle seems to replace \n using 


Can console launcher do this as well?