[
https://issues.apache.org/jira/browse/HBASE-24309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-24309:
----------------------------------
Looks like this one is cause of a new compiler warning. Reopening for addendum.
{noformat}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.hbase:hbase-examples:jar:2.3.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must
be unique: org.apache.hbase:hbase-common:jar -> duplicate declaration of
version (?) @ line 104, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
{noformat}
> 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)
