[
https://issues.apache.org/jira/browse/ACCUMULO-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350947#comment-14350947
]
Christopher Tubbs commented on ACCUMULO-3643:
---------------------------------------------
bq. If we have a @SupressWarnings annotation...
Some warnings cannot be avoided. For example, some unavoidable warnings about
compile-time annotation processors. You can't suppress those. And, javac
doesn't support the same suppression types as Eclipse (or other IDEs), so it
may look suppressed in one form, but it doesn't really suppress it from javac.
bq. We might also just want to run with -Xlint:-deprecation if that turns out
to be easier.
I believe I've already fixed all the deprecation warnings.
Regardless, we can certainly look into using {{-Werror}}, but it should not be
considered a prerequisite for findbugs checks. They are separate.
> Find more bugs with findbugs
> ----------------------------
>
> Key: ACCUMULO-3643
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3643
> Project: Accumulo
> Issue Type: Task
> Components: build
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Labels: findbugs
> Fix For: 1.7.0
>
>
> In version 1.6.0, we automated checking for bugs using findbugs with a
> maxRank of 6. I'd like to catch even more bugs by bumping the maxRank to at
> least 9.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
