[
https://issues.apache.org/jira/browse/LOG4J2-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110243#comment-14110243
]
Matt Sicker commented on LOG4J2-797:
------------------------------------
The problem with recommending it as a runtime dependency is you need it at
compile-time, too, if you have any custom plugins. It contains an annotation
processor that makes that possible without additional configuration. This could
be a rather confusing idea; personally, I'd make the API a provided dependency
and Core a runtime dependency (or provided) while integrating Log4j in my
container instead. Then again, that's a bit futuristic at this point.
> 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: [email protected]
For additional commands, e-mail: [email protected]
