Unfortunately I was not notified that you had answered my last question. In the meantime, I have found a good workaround for this bug. Doxygen allows you to designate a file so that the doxygen output will be written there. But the normal stderr also works when you specify this file. These are the details:
- The WARN_LOGFILE tag can be used to specify a file to which warning
- and error messages should be written. If left blank the output is written
- to stderr.
WARN_LOGFILE = doxygen.output
Then in the warnings plugin instead of having the MSBuild and doxygen parsers for the console you just specify the MSBuild parser.
In the "Scan workspace files" section of the Warnings plugin configuration, you specify the doxygen.output file with the doxygen parser.
It works like a charm. And you don't need to modify the regular expression to take into account the "[exec]" stuff that running doxygen through NAnt adds.