Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/177
I would not '@Ignore' the mongo tests. You could use a JUnit Assume that
skips the tests if an sys prop is set or something like that.
Note that the Jenkins builds are fine for now:
- 2.x https://builds.apache.org/view/L/view/Logging/job/Log4j%202%202.x/
- 3.x https://builds.apache.org/view/L/view/Logging/job/Log4j%202%203.x/
The tests pass on my machine but I understand that it can be a pain if they
do not on your set up.
---
