[jira] [Resolved] (LOG4J2-797) log4j-core should be listed as runtime dependency

["Remko Popma (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma resolved LOG4J2-797.
--------------------------------
    Resolution: Fixed

Pushed to master in commit 83953ba.
Please verify and close.

To answer your question: if my understanding is correct, configuring log4j-core as a runtime dependency (and not as a compile-time dependency) will have no adversary effect if you do not have custom plugins.

> log4j-core should be listed as runtime dependency
> -------------------------------------------------
>
>                 Key: LOG4J2-797
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-797
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 2.0.2
>         Environment: http://logging.apache.org/log4j/2.x/maven-artifacts.html
>            Reporter: whaefelinger
>            Assignee: Remko Popma
>            Priority: Minor
>             Fix For: 2.1
>
>
> The documentation (website: http://logging.apache.org/log4j/2.x/maven-artifacts.html) lists "log4j-core" as compile dependency (Gradle). 
> While this at not wrong, it does not hit the idea of api/core separation. Thus I suggest to list "log4j-core" as runtime dependency, i.e.
> {code}
> dependencies {
>   compile group: 'org.apache.logging.log4j', name: 'log4j-api', version: '2.0.2'
>   runtime group: 'org.apache.logging.log4j', name: 'log4j-core', version: '2.0.2'
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org