[
https://issues.apache.org/jira/browse/JENA-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825577#comment-13825577
]
Andy Seaborne commented on JENA-583:
------------------------------------
The thing that needs sorting is the big picture (JENA-191 is specifically the
module structure). We have isolated what the users sees to a single maven
artifact (apache-jena-libs) and a lib/ direcory in a download (apache-jena)
which is a step to being able to change the module structure.
IIRC logging control is used in testing and the command line utils. If logging
control put in a little helper module, then only the bits that need it can have
the dependency on logging provider.
While excluding and replacing log4j works, it not obvious from the dependency
tree.
> 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.1#6144)
