[
https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742955#comment-13742955
]
Nick Williams commented on LOG4J2-362:
--------------------------------------
There are actually several feature requests in JIRA's JIRA (is that like
inception?) to support attachment obsolescing. However, I did find this helpful
tidbit on a mailing list:
{quote}Trick: upload the file with exactly the same name, then the latest one
will be marked as "latest" (in mouse-over baloon), and earlier versions will be
shown in gray.{quote}
And this helpful tidbit on a JIRA, directly from a JIRA developer:
{quote}At the moment JIRA does allow one to attach files with the same name to
the issue and JIRA greys out the older files with the same name, such that
visually one can tell which attachment is the newest. Does this work for
you?{quote}
Try that?
> 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-1.png, whichjar-2.png, whichjar.png,
> whichjar-slf4j-1.png, whichjar-slf4j.png, whichjar.xlsx
>
>
> 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]
