viadee
As an IT-architect I want to see errors and warnings in a historical context, in order to see whether a development teams improves over time
This may take the form of small graphs with commits on the x axis and the number of issues on the y axis - probably small and both aggregated and per issue type. We would need some kind of persistence mechanism beyond a single status report though, which would increase the overall complexity, i.e. you can't do this a JUnit test whose results reside in the target folders of the team. Maybe this could be reasonably implemented as a Sonar plugin for vPAV reports?
In the current form (Maven plugin), we can create a file on the hardrive which will be re-read everytime we run vPAV. We can then store some key values (#issues, etc) and display the current history in the frontend.
The maven plugin approach is deprecated unfortunately. We would need to provide some other kind of storage outside the /target folder (which kind of breaks the Maven conventions) or build on the files in the target folder (like Sonar does with PMD etc.).
Such a file holding the historical contents could be stored in the resources folder, similar to the ruleSet.xml. In the first run we create the file and for further runs we read/write content to it, which in a later stage can be accessed to visualize historical data.