[
https://jira.codehaus.org/browse/MFINDBUGS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276859#comment-276859
]
Kohsuke Kawaguchi commented on MFINDBUGS-118:
---------------------------------------------
The root of the problem is that the output from findbugs:check is not
actionable for average developers.
Here is the scenario. Someone with sufficient Maven-fu integrates
findbugs:check into POM so so that the build will fail if some important
findbugs checkers fail. Two months later, Joe makes code changes and that
actually breaks the build. All Joe gets from Maven is rather unhelpful message
like this:
{noformat}
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:findbugs-maven-plugin:2.3.2:check (default-cli) on project
jenkins-core: failed with 24 bugs and 0 errors -> [Help 1]
{noformat}
... and he's on his own to actually figure out what those 24 bugs are.
This seems rather silly, when it is so easy for the mojo to also produce some
human readable report --- be it the summary in the console, HTML file in the
target directory, or anything that points Joe to the offending part of the
source code. Even just saying "run findbugs:gui to see the details of the
error" is better than nothing, because that points Joe to the right direction
without resorting to Google. I for one didn't know that I was supposed to run
findbugs:gui to see the reports (which unfortunately didn't work for me, as in
MFINDBUGS-147, but that's a separate story.)
> Add ability to show a summary of the bugs on the console
> --------------------------------------------------------
>
> Key: MFINDBUGS-118
> URL: https://jira.codehaus.org/browse/MFINDBUGS-118
> Project: Maven 2.x FindBugs Plugin
> Issue Type: New Feature
> Reporter: FabrÃcio Lemos
> Assignee: Garvin LeClaire
> Priority: Trivial
>
> It is really important if findbugs runs as part of the build cycle.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
