[
https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542218#comment-15542218
]
Andras Piros commented on OOZIE-1986:
-------------------------------------
I've sent an email to [*the author*|mailto:adjohnson...@gmail.com] requesting
license information and that [*the FindBugs JAR
file*|https://github.com/adjohnson916/findbugs-diff/releases/download/v0.1.0/findbugs-diff-0.1.0-all.jar]
should be put to Maven Central.
In the meanwhile the new patch does MD5 check in order we can go for sure the
downloaded JAR file is not tampered.
> 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
>
>
> 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)
