----- Original Message -----
From: "Conor MacNeill" <[EMAIL PROTECTED]>
[...]
> The idea would be that this page would provide a link to debug output,
> something like
> http://jakarta.apache.org/builds/gump/latest/dist-ant.html?debug
> which would provide the full Ant debug output. We could even support
> viewing
> at the verbose level. This may make it easier to understand some Gump
> failures such as the one currently occurring on jakarta-turbine-fulcrum.
>From my nightly build at work, for some projects I have XML output that
takes up to 7MB...(extreme case)
(All in all if I remember well, a complete build with all output and reports
(junit/metrics/audit) takes about 50MB and I have about a dozen of projects
to compile, some of them being C only, part C part Java and full Java)
In our intranet, when users come into the build result page they have a
warning in case there browser is not IE with a valid MSXML parser (need
MSXML3+) , if they want they can click directly on the XML page and the
browser displays the XML converted (on client side) via a tweaked log.xsl
available in Ant. For most cases it is OK and gives enough information for
end-users, however when I was doing setup the build system, nothing replaced
a direct look of the XML file...
Sometimes the collapsable view on XML file available on IE is very
convenient If you want to get your hands on the XSL that does this, just
type: res://msxml3.dll/DEFAULTSS.xsl in IE (or res://msxml.dll/DEFAULTSS.xsl
depending on your parser version)
Stephane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
