You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2016/11/12 05:49:58 UTC

[jira] [Closed] (LOG4J2-1698) Update LMAX Disruptor from 3.3.5 to 3.3.6

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

Gary Gregory closed LOG4J2-1698.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.8

In Git master. Local build OK.

{{mvn -pl !log4j-osgi clean test}} ran OK. Note there are still OSGi issues. I have local failures in the OSGi test module with or without this change but the Jenkins build passed before the commit for this issue.

> Update LMAX Disruptor from 3.3.5 to 3.3.6
> -----------------------------------------
>
>                 Key: LOG4J2-1698
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1698
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Gary Gregory
>            Assignee: Gary Gregory
>             Fix For: 2.8
>
>
> Update LMAX Disruptor from 3.3.5 to 3.3.6.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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