XSD for scoverage.xml

[RadoBuransky]

What about defining a schema for the report XML? I would check only basic stuff not to complicate further evolution. The issue is that sometimes people provide wrong XML to the Sonar plugin and it always takes me a while to find it out. The scalac plugin will always validate the generated file after creating and the Sonar plugin will validate it before using it.

[sksamuel]

Good idea. Can I change the xml format if needed first :)

On 3 June 2015 at 08:11, Rado Buranský notifications@github.com wrote:

What about defining a schema for the report XML? I would check only basic
stuff not to complicate further evolution. The issue is that sometimes
people provide wrong XML to the Sonar plugin and it always takes me a while
to find it out. The scalac plugin will always validate the generated file
after creating and the Sonar plugin will validate it before using it.

—
Reply to this email directly or view it on GitHub
#121.

[RadoBuransky]

Ha. Sure, just let me know then.

[deeplook]

Any progress on this? I'm trying to import the XML output in scoverage.xml into a custom test monitoring tool and it would be very useful to have some kind of specification about the XML, and be able to track changes. Something like the specification of the JUnit XML format )which actually points to this GitHub repo) comes into my mind, although it probably doesn't have to be that shiny.