|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sorry, this was not precise and needs some clarification: if I remove the special maven handling then the plug-in will still be usable in maven and freestyle jobs. Currently the findbugs plugin uses two different implementations: one gets instantiated by freestyle jobs and the other by maven jobs. In the warnings plugin I'm having only one implementation that is instantiated for both build types. This makes coding and testing much easier (DRY) and has no classloading problems. The only benefit for having a special maven implementation is to derive the filename of the findbugs warnings from the pom.