No thoughts on this?

On 28 Mar 2011, at 15:38, Phil Nash wrote:

> Hi,
> 
> I’m trying to integrate custom XML from a unit test tool into my
> cc.net log, but it always seems to add it as CDATA.
> It is well formed, valid, XML. I’ve tried it with and without an
> encoding PI (set both as UTF-8 and ANSI).
> I’ve tried specifying the file action as Copy, and leaving to the
> default.
> 
> My merge config looks like this:
> 
>       <publishers>
>               <merge>
>                       <files>
>                               <file>$(ArtifactsDirectory)\$(ProjectName)_INTRA
> \catch_results.xml</file>
>                       </files>
>               </merge>
>               <xmllogger logDir="$(BuildLogs)_$(ProjectName)_INTRA"/>
>               <statistics />
>               <modificationHistory  onlyLogWhenChangesFound="true" />
>       </publishers>
> 
> What I’ve noticed is that in the log I get a <buildresults> element
> with a <message> element containing the *closing* tag of my xml file.
> Then the rest of the file (ie, without the closing tag) is dumped as
> CDATA afterwards (unless I set the file action to “copy”, in which
> case it just disappears completely).
> 
> If it’s chopping the closing tag off that would explain why it treats
> it as CDATA (as it is no longer well formed).
> But why would it do that?
> I even tried emitted an extra newline on the end of my xml file – but
> that made no difference.
> 
> My xml format has no namespacing (the only similar report I found
> while googling traced their problem to a namespace).
> 
> Anything else I should be looking at?
> 
> This is Version : 1.6.7981.1, btw.
> 
> Thanks and regards,
> 
> [)o
> IhIL..

Reply via email to