Future of this plugin?

I think this plugin needs a new maintainer. If you want to be one, you can ask for commit access in Jenkins developer mailing list:
https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin

I may be interested in being a maintainer. But if so, I would make very big changes in it. My opinion is that the code is just to messy to fix. I will not spend more time [fixing things like this](https://github.com/jenkinsci/violations-plugin/commit/572bc1ce6fd3c7625978ca0c34d8d4ff95e6f8c4), and there is alot of that here.

I would suggest that:
- A library for parsing static code analasys reports is first developed. I've started [here](https://github.com/tomasbjerre/violations-lib).
- This plugin should use [analysis-core](https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins) to present the results.

And replace the current code with that implementation. That would make this plugin much less complex and maintainable.

What do you think?
@ryoichitaniguchi @rsommerard @MensObscura @nbruno @pfhorman @tandibar @wang-xinhong

Review the current plugin code alongside the referenced violations-lib and Jenkins analysis-core guidance. The proposed work is complete only when the plugin has been replaced with that library and analysis-core-based implementation, but the issue does not identify specific files or tests to begin with.

Written by the indexing model from the issue text.