You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Xu Cang (Jira)" <ji...@apache.org> on 2019/09/12 17:57:00 UTC
[jira] [Commented] (HBASE-22866) Multiple slf4j-log4j provider
versions included in binary package (branch-1)
[ https://issues.apache.org/jira/browse/HBASE-22866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928782#comment-16928782 ]
Xu Cang commented on HBASE-22866:
---------------------------------
question for [~vjasani] and [~apurtell]
this patch's hadoop-qa run had "shadedjars" with -1 and the patch is still committed. Do you already know the reason of this shadedjars failure?
The reason I am asking is I am trying to get HBASE-22804 committed but having the same shadedjars failure. And I am not sure how to add flag to show more info on HBase Jenkins to reveal which rule was offended. Thanks!
cc. [~caroliney14]
> Multiple slf4j-log4j provider versions included in binary package (branch-1)
> ----------------------------------------------------------------------------
>
> Key: HBASE-22866
> URL: https://issues.apache.org/jira/browse/HBASE-22866
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Andrew Purtell
> Assignee: Viraj Jasani
> Priority: Minor
> Fix For: 1.5.0, 1.3.6, 1.4.11
>
> Attachments: HBASE-22866.branch-1.000.patch, HBASE-22866.branch-1.000.patch
>
>
> Examining binary assembly results there are multiple versions of slf4j-log4j in lib/
> {noformat}
> slf4j-api-1.7.7.jar
> slf4j-log4j12-1.6.1.jar
> slf4j-log4j12-1.7.10.jar
> slf4j-log4j12-1.7.7.jar
> {noformat}
> We aren't managing slf4j-log4j12 dependency versions correctly, somehow.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)