Fix JUnit HTML reports collapsing whitespace in failure messages

[Copilot]

Browsers collapse consecutive whitespace by default, making failure messages with significant spacing (e.g. String s = (String)o; → String s = (String)o;) unreadable in generated JUnit HTML reports.

Changes

JUNIT.XSL

• Add code { white-space: pre-wrap; } CSS rule to preserve spaces and newlines inside <code> blocks
• Wrap @message output in <code> so the failure message inherits the same rule

<!-- Before -->
<xsl:value-of select="@message"/>

<!-- After -->
<code><xsl:value-of select="@message"/></code>

verify/ — self-contained verification helper (no build required)

• sample-results.xml: JUnit XML with intentional whitespace in failure messages
• verify.sh: transforms the sample XML with JUNIT.XSL and opens the result in a browser; supports WSL (explorer.exe), macOS (open), and Linux (xdg-open); requires xsltproc (sudo apt-get install xsltproc) or python3 + lxml

cd products/eclipse-junit-tests/src/main/scripts/verify
./verify.sh

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[fedejeanne]

@copilot how do I check if this PR does what it is supposed to do?

[Copilot]

@copilot how do I check if this PR does what it is supposed to do?

To verify this PR locally:

1. Build a JUnit XML result file (or use the one attached to the original issue) and run the JUNIT.XSL transform against it with Ant or any XSLT processor. The simplest way is to run the existing test build — the HTML reports are generated in testresults/html/.

2. Alternatively, you can download the attached test zip from the original issue, extract the XML file from it, and apply JUNIT.XSL to it.

3. Open the resulting HTML file in a browser and look at the "Type" column for the testFormatAll01 failure. With this fix, spaces are preserved — you should see String s = (String)o; (4 spaces) instead of String s = (String)o; (1 space), and the stack trace should show proper indentation.

Before (spaces collapsed):

After (spaces preserved):

Notice String s = (String)o; with 4 spaces in the message line, and proper indentation in the stack trace.

[fedejeanne]

Tested it locally, works as expected.

If there are no objections, I will merge this next week.

[HannesWell]

Tested it locally, works as expected.

How did you test it exactly?

Although it's not exactly related to this task, are you aware of the instructions how to test the build website locally?
https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/tree/master/sites/eclipse
In this case it doesn't help since the test-data download script doesn't download test results.

[fedejeanne]

How did you test it exactly?

@HannesWell I used a script generated by copilot in WSL. I put it in my own branch for you to test too, if you want:

• https://github.com/fedejeanne/eclipse.platform.releng.aggregator/tree/copilot/fix-junit-test-reports-2

[laeubi]

@fedejeanne please keep in mind this when working with copilot on platform repos:

https://github.com/eclipse-platform/.github/blob/main/CONTRIBUTING.md#using-github-copilot-agent

this prevents a lot of mail-traffic when some iterations are needed and you can later create a PR against the base easily instead of having the branches live in the main repository.