[
https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112792#comment-17112792
]
Ralph Goers edited comment on LOG4J2-2848 at 5/21/20, 4:36 AM:
---------------------------------------------------------------
I believe killing the Mongodb2 module needs to be included in this. I see no
need for Log4j to maintain 3 variations, especially when 2.x was declared EOL
in October 2016. The Apache repo stats show 194 downloads of Mongodb2 last
month. These numbers have been fairly flat for the last year. Given that no
changes will realistically ever be made to this module users can continue to
use the 2.13.3 release if they really need it.
was (Author: [email protected]):
I believe killing the Mongodb2 module needs to be included in this. I see no
need for Log4j to maintain 3 variations, especially when 2.x was declared EOL
in October 2016.
> Create module log4j-mongodb4 to use new major version 4 MongoDB driver
> ----------------------------------------------------------------------
>
> Key: LOG4J2-2848
> URL: https://issues.apache.org/jira/browse/LOG4J2-2848
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, MongoDB
> Reporter: Gary D. Gregory
> Assignee: Gary D. Gregory
> Priority: Major
>
> Create module log4j-mongodb4 to use new major version 4 Mongo driver since it
> breaks compatibility with the version 3 driver.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
