Hi Gert,
I'd think it would be best to group all types of failures under 1
'failure' tag. I see what you're saying about internal and build errors
having different structures though, maybe we could actually put your
second idea into a failure tag, e.g.
...
or
...
On
Hi Gert - thanks for the reply.
Regarding the xml structure, there's 2 things on my mind
- Try not to change the existing structure too much unless we have to
- This problem with exceptions is actually about failures generally
(I've tried using just a with a message and the same behaviour
manif
- Original Message -
From: "Mike Roberts" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
> The thing I get from this is that what we are losing is the failure
> message we have from the plain output and this failure message is
> reported outside of any targets or tasks. My sugg
Gert Driesen wrote:
- Original Message -
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 th
Mike,
I've modified the XmlLogger locally, to use the following xml layout to
report
build failures :
for build exceptions :
(if location information is available)
nested exception
for internal errors :
I've seen this same problem, not using CruiseControl, but instead recording
the log with the tag.
As a work around, I use an outer task that simply turns logging on and then
calls an inner task with the task to run a new instance of Nant.
This ensures that the results of the failed output make i
Mike,
This is a known issue
(http://sourceforge.net/tracker/index.php?func=detail&aid=788650&group_id=31
650&atid=402868), which is probably very easy to fix. But I was actually
waiting for a good proposal for the xml structure.
Taken from the existing bug report :
"Currently the layout of the
