hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-24309) Avoid introducing log4j and slf4j-log4j dependencies for modules other than hbase-assembly
Date Wed, 13 May 2020 10:50:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-24309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Duo Zhang resolved HBASE-24309.
-------------------------------
    Hadoop Flags: Reviewed
      Resolution: Fixed

Pushed to branch-2.3+.

Thanks [~stack] for reviewing.

> Avoid introducing log4j and slf4j-log4j dependencies for modules other than hbase-assembly
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-24309
>                 URL: https://issues.apache.org/jira/browse/HBASE-24309
>             Project: HBase
>          Issue Type: Sub-task
>          Components: logging, pom
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> In general, a library should not force the down stream users to use a specific logging
framework, and this is why there is a slf4j library.
> For HBase, since we also publish the testing-util module which almost depends on all
other sub modules, we should not introduce logging dependencies other than slf4j-api in these
modules. We should only add log4j dependencies in hbase-assembly and ship it with our binary
distribution.
> This is also important for switching to log4j2.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message