[
https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327075#comment-15327075
]
K P commented on LOG4J2-239:
This would indeed help for a log4j 1.x feature that is missing in log4j 2.x
See
[
https://issues.apache.org/jira/browse/LOG4J2-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327070#comment-15327070
]
K P commented on LOG4J2-1027:
-
This was possible in log4j 1.x
[
https://issues.apache.org/jira/browse/LOG4J2-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327037#comment-15327037
]
K P edited comment on LOG4J2-907 at 6/13/16 9:30 AM:
-
This would be a very welcome
[
https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327047#comment-15327047
]
K P commented on LOG4J2-1185:
-
This was indeed possible in log4j 1.x
(actually, we also rely on that, due to
[
https://issues.apache.org/jira/browse/LOG4J2-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327037#comment-15327037
]
K P commented on LOG4J2-907:
This would be a very welcome (actually needed) addition.
It was possible in