[
https://jira.codehaus.org/browse/MFINDBUGS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276652#comment-276652
]
Krzysztof Krason commented on MFINDBUGS-118:
--------------------------------------------
I don't know why this issue is marked as "Trivial" for me it is major or even
critical.
Here how a normal CI envoriment works (checkstyle, pmd, findbugs are attached
to the verify phase):
mvn clean install
If there are any errors the user that made the commit will get the mails with
console output, if there is nothing on the console then it doesnt exist :)
Going to the xml file, looking at it (which is BTW very messy, yeah I know that
it findbugs) and getting out the information what went wrong is quite
cumbersome.
Using GUI is of course not useful at all, who has run it more than once?
Normal way the code checking plugins work (checkstyle and pmd) is print the
error and print the files, lines and error description to the console.
I've been waiting for such feature in maven-findbugs-plugin for 2 years, please
add it.
> 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
