[
https://jira.codehaus.org/browse/MFINDBUGS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276863#comment-276863
]
Kohsuke Kawaguchi commented on MFINDBUGS-118:
---------------------------------------------
Upon reading the source code, I take the above comment back.
Despite what [all the configuration options in the documentation
page|http://mojo.codehaus.org/findbugs-maven-plugin/check-mojo.html] implies,
the findbugs:check mojo doesn't actually run findbugs at all. It merely reads
the report produced by earlier findbugs:findbugs and fails the build if that
contains any error. More over, if the file doesn't exist (meaning if the report
isn't run), it silently passes without issuing any error.
So if I just run "mvn clean install", the build will happily pass even if I
actually have findbugs errors (by virtue of not running FindBugs.) Or if I'm
iteratively working on fixing findbugs errors, I need to be running "mvn site"
to regenerate new reports or else findbugs:check will keep on failing the same
way.
> 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
