I have a regular Java compilation build that regularly has about 200 warnings.
When this build fails (early on, before the warnings would be generated), the
warnings plugin incorrectly assumes that the 200 warnings have been fixed, as
shown on the results page for particular build. The Compiler Warnings Trend
chart also shows a value of zero for that build. Both of these seem
non-intuitive and potentially misleading. For the Compiler Warnings Trend chart,
I would have expected to see something along the lines of what the Build History
Trend chart does, where failed build are marked red, so that the user knows that
the value in question (duration for Build History, warning count for Compiler
Warnings) may not be valid for that particular build. I'm not sure what should
be done about the case where the warnings are incorrectly counted as fixed on
the build results page.