[
https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742934#comment-13742934
]
Nick Williams commented on LOG4J2-362:
--------------------------------------
That diagram is extremely clear and helpful, Remko. Great job! Just a few minor
corrections:
# API and Core JARs should be "log4j-api-2.0.jar" and "log4j-core-2.0.jar,"
respectively. Not "log4j-2.0-api.jar" and "log4j-2.0-core.jar."
# For the API and Implementation you call them "Log4j-2.0 API" and "Log4j-2.0
Implementation", but for the legacy API you call it "Log4j 1.0 API." I would
omit the hyphen there. But I do agree with the placement of the number on the
name, in this diagram.
After reviewing it, two things occurred to me:
* Should we have the Log4j Tag Library JAR on here somewhere? I'm not
convinced, just wondering what others think.
* It looks like maybe there's a need for a jul-to-log4j-2.0 module? Having to
jump through the jul-to-slf4j then slf4j-api then log4j-slf4j-impl-2.0
artifacts seems like asking for performance issues.
> Add a diagram to the site that explains when to use which jar
> -------------------------------------------------------------
>
> Key: LOG4J2-362
> URL: https://issues.apache.org/jira/browse/LOG4J2-362
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.0-beta8
> Reporter: Remko Popma
> Fix For: 2.0-beta9
>
> Attachments: whichjar.png
>
>
> The log4j-2.0 download archive contains a number of jar files.
> It is not always immediately clear to new users which jar files they should
> use. A diagram should help to clarify this.
> Examples of the kind of diagram intended:
> http://www.slf4j.org/legacy.html
> http://wiki.apache.org/tomcat/FAQ/Logging
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
