[
https://issues.apache.org/jira/browse/HBASE-26803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502335#comment-17502335
]
Hudson commented on HBASE-26803:
--------------------------------
Results for branch master
[build #528 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/528/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/528/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/528/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Ban reload4j and logback dependencies
> -------------------------------------
>
> Key: HBASE-26803
> URL: https://issues.apache.org/jira/browse/HBASE-26803
> Project: HBase
> Issue Type: Task
> Components: dependencies, logging, pom
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-3
>
>
> Multiple logging framework on classpath can lead to strange behaviors, so we
> need to make sure that there is only one framework on our classpath.
> We used to ban log4j when switching to log4j2, now since hadoop is going to
> switch to reload4j for current release branches and zookeeper has switched to
> logback, we should exclude them too.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
