I can't offer a workaround or any insight into what's going on, but I can say we are seeing the same problem and if anyone can prioritise a fix or a workaround it would be appreciated.
Thanks. On Dec 10, 9:56 pm, John Wadlow <[EMAIL PROTECTED]> wrote: > I couldn't find an answer in this user group. I just upgraded from > 1.3 to 1.4. The build log is now wrapping acdatawith a ] ] (] > space ]) tags everytime there's anantfailure. I get the regular > build log when itnantpasses. > > It looks like the parser isn't handling the newline in the stack > trace. When I look at my build logs it always ends at the there. > > Example1 > > <![CDATA[<buildresults project="AvaTax"><message level="Info"><![CDATA > [Buildfile: file:///E:/ccnet/sustaining/avatax/build/master.build] ]> ... > <failure><builderror><type>NAnt.Core.BuildException</ > > type><message><![CDATA[External Program Failed: C:\Program Files\cvsnt > \cvs.exe (return code was 1)]]></message><location><filename>E:\ccnet > \avatax\build\include\release.build</filename><linenumber>347</ > linenumber><columnnumber>5</columnnumber></location><stacktrace><! > [CDATA[ atNAnt.Core.Tasks.ExternalProgramBase.ExecuteTask() > ]]></build> > > Example 2 > > <![CDATA[<buildresults project="AvaTax"><message level="Info"><![CDATA > [Buildfile: file:///E:/ccnet/sustaining/avatax/build/master.build] ]> ... > > <failure><builderror><type>NAnt.Core.BuildException</type><message><! > [CDATA[External Program Failed: C:\Program Files\Microsoft SQL Server > \90\Tools\Binn\SQLCMD.EXE (return code was 1)]]></ > message><location><filename>E:\ccnet\sustaining\avatax\build\include > \db.build</filename><linenumber>354</linenumber><columnnumber>4</ > columnnumber></location><stacktrace><![CDATA[ > atNAnt.Core.Tasks.ExternalProgramBase.ExecuteTask() > ]]></build> > > The correct stacktrace use to look like this > > <stacktrace> > <![CDATA[ atNAnt.Core.Tasks.ExternalProgramBase.ExecuteTask() > atNAnt.Core.Tasks.ExecTask.ExecuteTask() > atNAnt.Core.Task.Execute() > atNAnt.Core.Target.Execute() > atNAnt.Core.Project.Execute(String targetName, Boolean > forceDependencies) > atNAnt.Core.Tasks.CallTask.ExecuteTask() > atNAnt.Core.Task.Execute() > atNAnt.Core.TaskContainer.ExecuteChildTasks() > atNAnt.Core.TaskContainer.ExecuteTask() > atNAnt.Core.Task.Execute() > atNAnt.Core.Tasks.LoopTask.ExecuteChildTasks() > atNAnt.Core.Tasks.LoopTask.DoWork(String[] propVals) > atNAnt.Core.Tasks.LoopTask.ExecuteTask() > atNAnt.Core.Task.Execute() > atNAnt.Core.Target.Execute() > atNAnt.Core.Project.Execute(String targetName, Boolean > forceDependencies) > atNAnt.Core.Tasks.CallTask.ExecuteTask() > atNAnt.Core.Task.Execute() > atNAnt.Core.Target.Execute() > atNAnt.Core.Project.Execute(String targetName, Boolean > forceDependencies) > atNAnt.Core.Tasks.CallTask.ExecuteTask() > atNAnt.Core.Task.Execute() > atNAnt.Core.Target.Execute() > atNAnt.Core.Project.Execute(String targetName, Boolean > forceDependencies) > atNAnt.Core.Project.Execute() > atNAnt.Core.Project.Run()]]></stacktrace> > > Does anyone have any idea what's going on or a work around?
