[
https://issues.apache.org/jira/browse/LOG4J2-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110651#comment-14110651
]
Matt Sicker commented on LOG4J2-797:
------------------------------------
The annotation processor is for caching the location of all your plugins.
Otherwise, we need to do runtime package scanning and other fun reflection that
slows down start-up time. See LOG4J2-798 about that.
As to documenting that, however, I agree. It's a good idea to mention that
outside the API JAR(s), you don't really need the others at compile time. Do
you have any suggested changes to the docs? Like where in the manual to go over
this, patches, etc.?
> 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]
