On Thu, Aug 4, 2011 at 1:52 PM, Brad Stiles <[email protected]> wrote: > I have confirmed that 1.6 exhibits the same behavior as 1.5 with > regard to this issue. Here is my command line: > > ccnet.exe /config:configfilename /validate /logging:off > /errorpause:off /remoting:off > > Am I doing something wrong? > > I'm calling it from a NAnt script, because I'm also checking out from > a subversion repository, and then copying the file elsewhere if > successful. > > To be clear, the validation works, and the "build" shows as > successful, but posts these warnings that make it look like something > went wrong.
OK, so rather than using ccnet.exe to validate the configuration file, I tried using the CCValidator program, but it does not write the complete error message out to the log file when I use the --logfile option. For instance, if I run without the --nogui option and no log file, I get this output in the GUI: * The configuration file contains invalid xml: <filename> * The 'project' start tag on line 15 does mat match the end tag of 'cruisecontrol'. Line x, position 3. However, when I redirect to a log file using the --logfile option, I only get the first line, and not the second. I'm trying to set up a build to check the confguration file before exporting it from my repository and rejecting it if it has errors. How do I get the second line in my log file so that I can present it to the users?
