We're doing incremental Maven multi-module builds in Hudson (m2 job type), and I've noticed the following behavior: When a particular module in the multi-module build doesn't run (because it hasn't changed), the static analysis plugins for the top-level build report that all of that module's warnings, FindBugs issues, etc. have been resolved. I understand why this is happening, but it's a bit frustrating – the only way we can get accurate trending for static analysis reports is by forcing a full (and lengthy) rebuild whenever any module is changed.

Theoretically, couldn't the analysis utilities recognize builds that didn't execute (as opposed to builds that failed) and use the results from the most recent executed build? It seems (although I have no idea what the code looks like) as if those results should be available in some form, since they're necessary to generate the trend graphs.