My understanding is that the warnings plugin will apply all its parsers against
Hudson's log files. For us, this has lead to the problem of false positives in
the warnings results.

We are using the Eclipse compiler after upgrading the warnings plugin from our
local hacked version (I added Eclipse compiler support I while ago) to 1.19, we
are now getting false warnings from the MSBuild parser generated by log lines
that have nothing to do with compilation.

It would be great if we could control which parsers are used during the run of
the warnings plugin.