[
https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588676#comment-15588676
]
Abhishek Bafna commented on OOZIE-1986:
---------------------------------------
I guess issue is because of the missing execute flag in file permissions.
Please check. Thanks.
{noformat}
-rwxr-xr-x 1 abafna staff 4292 Oct 10 17:38 test-patch-10-compile
-rw-r--r-- 1 abafna staff 9381 Oct 19 11:15 test-patch-11-findbugs-diff
-rw-r--r-- 1 abafna staff 33 Oct 19 11:15
test-patch-11-findbugs-diff-0.1.0-all.jar.md5
-rwxr-xr-x 1 abafna staff 3471 Jan 25 2016
test-patch-15-backwards-compatibility
{noformat}
> 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)
