hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12289) Make sure slf4j-log4j12 jar is not in classpath
Date Tue, 10 Nov 2015 21:37:10 GMT

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

Ashutosh Chauhan commented on HIVE-12289:
-----------------------------------------

There is no direct dependency of slf4j-log4j12 declared in our poms. So, I am not sure where
to add that scope. We are getting slf4j-log4j12 transitively from other deps.

> Make sure slf4j-log4j12 jar is not in classpath
> -----------------------------------------------
>
>                 Key: HIVE-12289
>                 URL: https://issues.apache.org/jira/browse/HIVE-12289
>             Project: Hive
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.0.0
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-12289.2.patch, HIVE-12289.3.patch, HIVE-12289.4.patch, HIVE-12289.patch
>
>
> log4j12 which is version 1.2 gets pulled in by transitive dependency. Need to make sure
we only have log4j2 is in classpath, otherwise slf4j may bind to version 1.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message