Róbert Papp

For reference https://github.com/TWiStErRob/net.twisterrob.sun/tree/bcbd0a53129742904ea74294fb55a871db01f4e0 will give us this state. Execute ```shell gradlew :feature:configuration:recordPaparazziDebug -Pnet.twisterrob.build.screenshot-tests=true ```

Wonder if slapping a CDATA around it would "fix" this, or show the `` literally.

See https://github.com/cashapp/paparazzi/pull/293

Slight alpha/dimming could be enough, doesn't necessarily need to change structure.

Please link the YouTrack issue in the PR description for the curious.

Do I understand correctly that this limitation exists because you're parsing the `dependencies` blocks rather than hooking into the resolved [configurations](https://docs.gradle.org/current/dsl/org.gradle.api.Project.html#org.gradle.api.Project:configurations) Gradle provides in-memory? Or is the limitation only "auto-removing"...

@bobleujr see also https://github.com/EnricoMi/publish-unit-test-result-action/issues/12#issuecomment-735673865 Can we link them in community?

FYI: might be related slightly https://github.com/github/feedback/discussions/13480

I've been playing around with attributing JUnit XML to lines in a repo, I got this far:  If the top of the stack trace contains a filename, that can...

Nice! Shall we close this? The hiding part might be an extra scope to #41.