Skip to content

Remove org.apache.logging.log4j dependencies #2

Open
@arichiardi

Description

@arichiardi

From my (limited) experience 😄 with Java log, it looks like the org.apache.logging.log4j dependencies are only necessary at runtime.

It makes sense, the logger is a Java service and it is resolved at runtime, version and all. For instance in my project I have:

                [org.apache.logging.log4j/log4j-api "2.6.2" :scope "runtime"]
                [org.apache.logging.log4j/log4j-core "2.6.2" :scope "runtime"]
                [org.apache.logging.log4j/log4j-jcl "2.6.2" :scope "runtime"]
                [org.apache.logging.log4j/log4j-jul "2.6.2" :scope "runtime"]
                [org.apache.logging.log4j/log4j-1.2-api "2.6.2" :scope "runtime"]
                [org.apache.logging.log4j/log4j-slf4j-impl "2.6.2" :scope "runtime"]  

See the :scope? Everything is working fine. For this reason I would suggest to patch project.clj, remove the deps and let the app using your lib decide the implementation to hook.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions