logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4J2-724) log4j-bom does not include lmax-disruptor
Date Fri, 25 Jul 2014 05:41:38 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma resolved LOG4J2-724.
--------------------------------

    Resolution: Not a Problem

Resolving this issue as "not a problem". Please feel free to re-open if you disagree or close
this issue if you are happy with the explanation.

> log4j-bom does not include lmax-disruptor
> -----------------------------------------
>
>                 Key: LOG4J2-724
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-724
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 2.0
>         Environment: Any; Observed on OSX Macbook Air
>            Reporter: Dirk J Harrington
>            Priority: Minor
>             Fix For: 2.0.1
>
>
> log4j v2 introduced async loggers and also a BoM. However, the LMAX Disruptor dependency
is not listed in the BoM.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message