[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118384#comment-14118384
]
Robert Kanter commented on OOZIE-1793:
--------------------------------------
Ah, I didn't see that. I think it should be okay because:
# You can build Oozie, docs, etc with Java 6 still. Users shouldn't need to
run findbugs, that's really more for us devs, and we'll know to use JDK 7. And
it's only in trunk.
# Eventually, we'll want to drop support for 1.6 (e.g. Hadoop 2.6 is the last
release to support 1.6)
# It's probably best if we use the latest version of findbugs.
The only downside is that I think the pre-commit build runs with Java 6, so
OOZIE-1986 will have to wait for that machine to be updated.
What do you think?
> Improve find bugs reporting for Oozie
> -------------------------------------
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Improvement
> Components: build
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: 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)
