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

Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/04/21 10:17:00 UTC

[jira] [Commented] (HBASE-26965) Replace fully qualified class names with import statements where possible

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

Duo Zhang commented on HBASE-26965:
-----------------------------------

For some logging related tests, I used this trick to use the log4j2 related classes, FYI.

> Replace fully qualified class names with import statements where possible
> -------------------------------------------------------------------------
>
>                 Key: HBASE-26965
>                 URL: https://issues.apache.org/jira/browse/HBASE-26965
>             Project: HBase
>          Issue Type: Task
>            Reporter: Nick Dimiduk
>            Priority: Major
>
> Over on HBASE-26954, it was noticed that our enforcer check missed a class. Turns out, the restrict-imports enforcer-rule only works on import statements. Let's take a pass for fully qualified classes uses outside of import statements and see if we can reduce their number, so as to avoid this type of mistake in the future.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)