Currently, the warnings plugin is not invoked after a project failed before,
i.e. during execution of an ant task. Hence warnings / errors found in the logs
will never be displayed on the dashboard. I would like to mention that in my
opinion this is propably not the desired behavior for several users.
I.e. me and my developers make intensive use of the dashboard in order to get a
quick overview on the warnings AND errors issued by the compiler (in our case;
it is an ant job that launches a devenv on native c++ code -> hence a MSBUILD
styled log is generated). This is a great benefit over struggling through tons
of plain build log output that in general got totally mixed up due to concurrent
Hence, I would like to strongly vote for an option that allows the user of the
plugin to decide whether to collect (and display) warnings on the dashboard or
skipping this plugin's executing on fail (in order not to break the CI game).