Re: [nant-dev] Setting message level output from programs

2008-07-23 Thread Robin McKenzie
Gert, My mistake, I had assumed that "Invoking D:\data\Build\BuildHelperLib.dll : Acturis.HelperLib.XmlFileUtil.AttributeTransformXmlFile" meant that AttributeTransformXmlFile was being called directly, but it was actually another method (Program.Main, which I presume is the default within .NE

Re: [nant-dev] Setting message level output from programs

2008-07-23 Thread Robin McKenzie
Gert, Many thanks for the suggestion - I've updated my code so that the top-level public method includes: try { CallSubMethod(params); } catch (Exception e) {

Re: [nant-dev] Setting message level output from programs

2008-07-23 Thread Gert Driesen
Hey Robin, Currently, the exec task will log all output that the external process writes to stderr as warnings. I don't think we should consider all output to stderr as actual errors. I'd suggest fixing your buildhelper to return a non-zero exit code when execution fails. Gert From:

[nant-dev] Setting message level output from programs

2008-07-23 Thread Robin McKenzie
Hi, I'm interested in finding out how an external program, run through the NAnt command can produce elements in the log file with a level other than "Warning". My build file contains: