Rob,

Heads up on something I came across and hopefully haven't broken.

jena-jdbc-core directly uses Log4j to setup logging if configured to do so.
org.apache.jena.jdbc.JenaDriver

I've put in a dependency which is still transitive so that nothing should have changed.

jena-jdbc-driver-mem and jena-elephas have a testing dependency and that should be OK.

[[ jena-jdbc-driver-mem ::
  // Unfortunately, this code "knows" how log4j was set up in testing
  // Thsi is fragile.
]]

        Andy


On 18/02/16 16:47, Andy Seaborne (JIRA) wrote:

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

Andy Seaborne commented on JENA-583:
------------------------------------

This is done subject to testing.

jena-cmds depends on a slf4j binding for the command line tools.  Depending on 
this should still pull in slf4-log4j12 and log4j and they then get into 
apache-jena, the binary download that includes the command line tools.

jena-fuseki-core depends on having some logging command line and also default 
server setup should still include them at the moment.

jena-jdbc-core has explicit calls to Log4j configuration. For stability,  
direct dependency has been added.

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)


Reply via email to