[ 
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504075#comment-15504075
 ] 

Rohini Palaniswamy commented on OOZIE-1793:
-------------------------------------------

+1. Good to have this added.

> Improve find bugs reporting for Oozie
> -------------------------------------
>
>                 Key: OOZIE-1793
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1793
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Blocker
>             Fix For: 4.3.0
>
>         Attachments: OOZIE-1793-01.patch, OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie.  And even if it does 
> work, it looks like it's just going to create an XML file.  
> Based on some minor refactoring to this 
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
>  and this [stack overflow 
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
>  I was able to improve our findbugs reporting.  Now, when you run {{mvn 
> verify}} (which we use to generate a checkstyle report), it will also run 
> findbugs and transform the resulting XML files into html files that are human 
> readable.
> The hard part here will be actually going through the reports and fixing 
> these bugs; but that's for other JIRAs :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to