[
https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016096#comment-17016096
]
Konstantin Gribov commented on TIKA-3019:
-
[~rgoers], yes, I mentioned {{log4j1.compatibility}}
[
https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015394#comment-17015394
]
Ralph Goers commented on TIKA-3019:
---
FWIW - Log4j 2.13.0 includes experimental support for Log4j 1.2
[
https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17013000#comment-17013000
]
Konstantin Gribov commented on TIKA-3019:
-
[~tallison], there seems to be actually twofold issue
[
https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010973#comment-17010973
]
Tim Allison commented on TIKA-3019:
---
Got it. That was my understanding as well. If we remove log4jx 1x
[
https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010262#comment-17010262
]
Kenneth William Krugler commented on TIKA-3019:
---
Hi [~tallison] - if we're explicitly using
[
https://issues.apache.org/jira/browse/TIKA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009148#comment-17009148
]
Tim Allison commented on TIKA-3019:
---
IIUC, the fix for this would be to swap out slf4j-log4j12 for
