You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2016/10/24 13:40:58 UTC
[jira] [Reopened] (OOZIE-1986) Add FindBugs report to pre-commit
build
[ https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andras Piros reopened OOZIE-1986:
---------------------------------
Some MD5 related issue is present, plus some more fixes for the case in the patch there is a new Maven module born / an old one was killed.
> 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
> Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-1986.001.patch, OOZIE-1986.002.patch, OOZIE-1986.003.patch, OOZIE-1986.004.patch, OOZIE-1986.005.patch, OOZIE-1986.006.patch, OOZIE-1986.007.patch, OOZIE-1986.008.patch, OOZIE-1986.009.patch, OOZIE-1986.010.patch, summary.txt
>
>
> 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)