[jira] [Commented] (JENA-583) Get rid of log4j dependency in jena-core

["Hendy Irawan (JIRA)" <ji...@apache.org>]

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

Hendy Irawan commented on JENA-583:
-----------------------------------

+1 for this :)

Excluding these dependencies from app is a good workaround since it's low effort anyway.

At first I wanted to propose using Maven {{<profile>}} to separate the command line dependencies from normal dependencies, but that's not such a good idea, the better way would be separation of modules at Jena level.

At least now I know why log4j is depended by Jena. :)

> 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.2#6252)