[
https://issues.apache.org/jira/browse/LOG4J2-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067305#comment-14067305
]
Remko Popma commented on LOG4J2-724:
------------------------------------
The BOM provides only the versions of all the artifacts that are created in
log4j2. I don't pretend to be an expert on this subject but this is consistent
with the [Maven
page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]
that mentions BOMs.
The LMAX Disruptor dependency is only needed if you want to use Async Loggers.
There are a number of optional dependencies that you may or may not need
depending on what feature of log4j2 you want to use. They are all listed on the
web site. For example, these are the dependencies for log4j-core:
[http://logging.apache.org/log4j/2.x/log4j-core/index.html|http://logging.apache.org/log4j/2.x/log4j-core/index.html]
> 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: [email protected]
For additional commands, e-mail: [email protected]
