How is the current implememtation working? Is this a text or xml file that is parsed and then gets visualized?

A simple solution would be to just implement a parser for the warnings plugin. Of course using analysis-core would work, too.

What do you think?

In order of preference:

1. make the static analysis collector, et al have a tool agnostic generic mechanism for reporting issues with tool provided types and categories.
(along the lines of xUnit where all test results are normalized to a common form?)
2a. have an xslt that transforms klocwork xml format to the already handled findbugs format or
2b. (this request) add klocwork as another tool using SA/AC
3. have warnings plugin be able to publish a portlet like SA's warnings (trend by type and per project) where the types of each built in or ad hoc parser gets its on line/column (another request made a few weeks back).
4. (what I'm currently doing) is a bunch of adhoc console parsers based on the text report from klocwork.

What I have works, but I thing any of 1 2 or 3 would obviously be a better foundation not just for klocwork, but for any other tool producing analysis results.

The plugin is deprecated and not maintained anymore. Please upgrade to the warnings-ng plugin.