[
https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165422#comment-16165422
]
ASF subversion and git services commented on LOG4J2-2035:
---------------------------------------------------------
Commit d90840072c33dc07ba68583e07abde47416aa62f in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d908400 ]
LOG4J2-2035 Fix documentation to clarify disruptor-3.3.4 is now required for
async loggers: disruptor-3.3.3 was never released.
> There is no such lib as disruptor-3.3.3
> ---------------------------------------
>
> Key: LOG4J2-2035
> URL: https://issues.apache.org/jira/browse/LOG4J2-2035
> Project: Log4j 2
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 2.9.0
> Reporter: Leonid Bogdanov
> Assignee: Remko Popma
> Priority: Trivial
>
> Async logging configuration page says "Log4j-2.9 and higher require
> disruptor-3.3.3.jar or higher on the classpath", but there is no such version
> of the disruptor lib in the Maven Central, after 3.3.2 comes 3.3.4.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
