You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "whaefelinger (JIRA)" <ji...@apache.org> on 2014/08/25 12:31:57 UTC

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

whaefelinger created LOG4J2-797:
-----------------------------------

             Summary: 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
            Priority: Minor


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

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