accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2903) Monitor depends on undefined log4j-over-slf4j dependency
Date Wed, 18 Jun 2014 17:48:25 GMT

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

Christopher Tubbs commented on ACCUMULO-2903:
---------------------------------------------

I'm not sure what dropwizard is, but the point of the log4j-over-slf4j is when you have some
code that is using the log4j API (often because it's in a dependency that you don't have control
over), but you prefer to use slf4j with something other than log4j (eg. logback). What you'd
do in that case is exclude all the log4j implementation jars from the classpath and include
the alternate implementation of log4j (log4j-over-slf4j) which redirects log4j API to slf4j,
which then would go to whatever slf4j logger implementation you've put on the classpath. (log4j
-> slf4j -> logback). You wouldn't use log4j-over-slf4j if your logging looks like (slf4j
-> log4j). If it's being pulled in transitively, it should be excluded.

> Monitor depends on undefined log4j-over-slf4j dependency
> --------------------------------------------------------
>
>                 Key: ACCUMULO-2903
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2903
>             Project: Accumulo
>          Issue Type: Bug
>          Components: build
>            Reporter: Josh Elser
>            Priority: Trivial
>              Labels: newbie
>
> Added a dependency to the monitor to test something and I noticed some compilation failures.
> It appears that we don't depend on org.slf4j.log4j-over-slf4j like we should. This should
(likely) be the same slf4j version that we're depending on in the parent pom.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message