[
http://jira.codehaus.org/browse/MFINDBUGS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233153#action_233153
]
Robert Scholte commented on MFINDBUGS-118:
------------------------------------------
>From [maven-surefire-plugin:test useFile parameter|
>http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#useFile]
{quote}
Option to generate a file test report or just output the test report to the
console.
Default value is: true.
{quote}
{{useFile}} has nothing to do with printing to the console or not.
Personally I don't like to mix building and reporting. Surefire might report a
bit more to the console then the findbugs-plugin, but it is the default plugin
bound to the test-phase. Failing tests are always blockers, so showing this
info could be justified for that reason.
Findbugs, checkstyle, pmd are all code quality plugins with a {{check}} goal to
block a build and some report goal to show all results.
FYI: it is possible to just execute {{mvn findbugs:findbugs}} instead of {{mvn
site}} if you only want to update this report.
> Add ability to show a summary of the bugs on the console
> --------------------------------------------------------
>
> Key: MFINDBUGS-118
> URL: http://jira.codehaus.org/browse/MFINDBUGS-118
> Project: Maven 2.x FindBugs Plugin
> Issue Type: New Feature
> Reporter: FabrÃcio Lemos
>
> It is really important if findbugs runs as part of the build cycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
