----- Original Message -----What does the plain formatter do? I'm not too worried as long as (at least) the top level problem / location is available.
From: "Mike Roberts" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Should we only output the message of an exception, or also the stacktrace ? How should we represent nested exceptions in the xml log?
should we have something like this ?
<buildfailure> <location> ... </location> <message> ... </message> <stacktrace> ... </stacktrace> <buildfailure> <location> ... </location> <message> ... </message> <stacktrace> ... </stacktrace> </buildfailure> </buildfailure>
should we only output the stacktrace for the "top" exception ?
should we use <internalfailure> for internal errors (non-buildexceptions) or
use <failure type="build | internal"> ? Only buildexceptions have a
location, so the location element would only be valid for them.
Optionally, it would be nice to add an attribute to the 'buildresults'Can we do this in a tag at the end then? <success>true</success> or something?
root tag called 'success' that is either "true" or "false".
We can't do this, as the xml is not buffered.
Cool. The only reason I mentioned the units was because the plain formatter outputs it.It would also be good to introduce a <time units="seconds"> tag, thatyes, this would definitely be useful, but I guess it should be called
could be used both underneath the top level to indicate the time for the
whole build, and maybe also for each target to show how long each target
takes.
something like elapsedtime or buildtime ... and not sure if we need the
units attribute
Mike
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
