You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Brian McDevitt (JIRA)" <ji...@apache.org> on 2018/09/05 20:58:00 UTC

[jira] [Commented] (KUDU-2409) Fix Java style checkers and linters

    [ https://issues.apache.org/jira/browse/KUDU-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604933#comment-16604933 ] 

Brian McDevitt commented on KUDU-2409:
--------------------------------------

[~granthenke] do you have have preference on which of the static analysis tools should be worked on first?

> Fix Java style checkers and linters
> -----------------------------------
>
>                 Key: KUDU-2409
>                 URL: https://issues.apache.org/jira/browse/KUDU-2409
>             Project: Kudu
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Grant Henke
>            Assignee: Grant Henke
>            Priority: Major
>
> Currently our Java build supports code quality checks like checkstyle but does not enable them to break the build because we have too many existing issues.
> This Jira is to track:
>  * Fixing checkstyle issues
>  * Fixing findbugs issues (change to SpotBugs?)
>  * Fixing PMD issues
>  * Fixing Javadoc linter issues
>  * Fixing un-annotated deprecated and unsafe usages
>  * Adding flags to detect/prevent the issues in the future
> Note: We may also want to prevent the use of some packages/classes. For example we could prevent the use of "com.google.common.annotations.VisibleForTesting" given that Yetus is our audience interface annotation library of choice.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)