Peter Reilly wrote:
The google-test people are going to to change the output from
to
(with a command-line switch).
They have some extra attributes, and do not populate some attributes
and elements. but the output is understood by hudson without mod to
hudson.
well, all the tools are one XSL
The google-test people are going to to change the output from
to
(with a command-line switch).
They have some extra attributes, and do not populate some attributes
and elements. but the output is understood by hudson without mod to
hudson.
Peter.
On Wed, Mar 18, 2009 at 3:50 PM, Jesse Glick
Peter Reilly wrote:
a question that has been asked a number of times on the hudson mailing list is
what is the schema of the xml that junit generates.
BTW:
https://hudson.dev.java.net/nonav/issues/show_bug.cgi?id=3007
-
To
Peter Reilly wrote:
In any case, here is a first attempt at a schema for junit (in relaxng
compact syntax)
If you are going to declare an official schema, I would recommend making and enforce it at runtime, at least in development builds (or if assertions
are enabled etc.). Otherwise the dan
Looks good to me.
Might be worth to add it to src/etc.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
a question that has been asked a number of times on the hudson mailing
list is what
is the schema of tthe xml that junit generates.
I have had a quick look at the code, and noticed that there two related schemas.
1) the xml that generates
and
2) the xml that uses internally.
Both these formats
