[
https://issues.apache.org/jira/browse/JENA-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152570#comment-15152570
]
ASF subversion and git services commented on JENA-583:
------------------------------------------------------
Commit 1d12a1edce4569237af96254a620800c7ecbd632 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1d12a1e ]
JENA-583: Make log4j and slf4j-log4j12 <optional>
This closes #117.
> Get rid of log4j dependency in jena-core
> ----------------------------------------
>
> Key: JENA-583
> URL: https://issues.apache.org/jira/browse/JENA-583
> Project: Apache Jena
> Issue Type: Improvement
> Components: Jena
> Affects Versions: Jena 2.11.0
> Reporter: Francis De Brabandere
> Labels: logging
>
> Apache jena core seems to pull in log4j and slf4j-log4j12, since you use
> slf4j I would suppose I can plug in my own logging backend. If you have a
> hard dependency on log4j at least make it optional and don't force it in the
> core jena components.
> Ultimately this avoids these kinds of issues:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:.../target/universal/stage/lib/ch.qos.logback.logback-classic-1.0.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:.../target/universal/stage/lib/org.slf4j.slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type
> [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
