[ 
https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-1986:
---------------------------------
    Description: 
Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
build generate a findbugs report.  It should probably before and after the 
patch and only complain it there are more after.  And it should link to the 
report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
easy to identify the new findbugs items.

You can generate the findbugs reports by running:
{noformat}
mvn verify -DskipTests
{noformat}
This also runs checkstyle

  was:
Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
build generate a findbugs report.  It should probably before and after the 
patch and only complain it there are more after.  And it should link to the 
report.

You can generate the findbugs reports by running:
{noformat}
mvn verify -DskipTests
{noformat}
This also runs checkstyle


> Add findbugs report to pre-commit build
> ---------------------------------------
>
>                 Key: OOZIE-1986
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1986
>             Project: Oozie
>          Issue Type: Bug
>          Components: tests
>            Reporter: Robert Kanter
>
> Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
> build generate a findbugs report.  It should probably before and after the 
> patch and only complain it there are more after.  And it should link to the 
> report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
> easy to identify the new findbugs items.
> You can generate the findbugs reports by running:
> {noformat}
> mvn verify -DskipTests
> {noformat}
> This also runs checkstyle



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

Reply via email to