[jira] [Commented] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435497#comment-16435497 ] Martin commented on LOG4J2-548: --- It's been more than a year since the patch was suggested. W

[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435497#comment-16435497 ] Martin edited comment on LOG4J2-548 at 4/12/18 12:53 PM: - It's bee

[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435497#comment-16435497 ] Martin edited comment on LOG4J2-548 at 4/12/18 12:54 PM: - We have

[jira] [Comment Edited] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435497#comment-16435497 ] Martin edited comment on LOG4J2-548 at 4/12/18 12:57 PM: - We have

[jira] [Created] (LOG4J2-2270) Strings::join, when called with [null] returns "null" instead of EMPTY

Cyril Martin created LOG4J2-2270: Summary: Strings::join, when called with [null] returns "null" instead of EMPTY Key: LOG4J2-2270 URL: https://issues.apache.org/jira/browse/LOG4J2-2270 Project: Log4j

[jira] [Commented] (LOG4J2-2270) Strings::join, when called with [null] returns "null" instead of EMPTY

[ https://issues.apache.org/jira/browse/LOG4J2-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376270#comment-16376270 ] Cyril Martin commented on LOG4J2-2270: -- Thank you. Cyril Martin > Strings::join, w

[jira] [Closed] (LOG4J2-2270) Strings::join, when called with [null] returns "null" instead of EMPTY

[ https://issues.apache.org/jira/browse/LOG4J2-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cyril Martin closed LOG4J2-2270. > Strings::join, when called with [null] returns "null" instead of EMPTY >

[jira] [Commented] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653048#comment-16653048 ] Chris Martin commented on LOG4J2-1479: -- Hi- [~mikaelstaldal] I've started work on

[jira] [Created] (LOG4J2-2981) OnStartupTriggeringPolicy only rolls over when minsize = 0

Samuel Martin created LOG4J2-2981: - Summary: OnStartupTriggeringPolicy only rolls over when minsize = 0 Key: LOG4J2-2981 URL: https://issues.apache.org/jira/browse/LOG4J2-2981 Project: Log4j 2

[jira] [Created] (LOG4J2-2984) Filters are not applied to loggers

Samuel Martin created LOG4J2-2984: - Summary: Filters are not applied to loggers Key: LOG4J2-2984 URL: https://issues.apache.org/jira/browse/LOG4J2-2984 Project: Log4j 2 Issue Type: Bug

[jira] [Updated] (LOG4J2-2984) Filters are not applied to loggers

[ https://issues.apache.org/jira/browse/LOG4J2-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Martin updated LOG4J2-2984: -- Description: According to the documentation, Filters can be applied in different places: amon

[jira] [Updated] (LOG4J2-2984) Filters are not applied to loggers

[ https://issues.apache.org/jira/browse/LOG4J2-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Martin updated LOG4J2-2984: -- Affects Version/s: 2.0 2.0.1 2.0.2

[jira] [Updated] (LOG4J2-2984) Filters configured in Logger aren't applied at all; global filters can't DENY

[ https://issues.apache.org/jira/browse/LOG4J2-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Martin updated LOG4J2-2984: -- Description: According to the documentation, Filters can be applied in different places: amon

[jira] [Commented] (LOG4J2-2984) Filters configured in Logger aren't applied at all; global filters can't DENY

[ https://issues.apache.org/jira/browse/LOG4J2-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255316#comment-17255316 ] Samuel Martin commented on LOG4J2-2984: --- I have updated the issue (and the title)

[jira] [Commented] (LOG4J2-2984) Filters configured in Logger aren't applied at all; global filters can't DENY

[ https://issues.apache.org/jira/browse/LOG4J2-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292384#comment-17292384 ] Samuel Martin commented on LOG4J2-2984: --- What you say seems reasonable. Moreover,

[jira] [Created] (LOG4J2-3207) Move JNDI / network lookups out of the core module

Ches Martin created LOG4J2-3207: --- Summary: Move JNDI / network lookups out of the core module Key: LOG4J2-3207 URL: https://issues.apache.org/jira/browse/LOG4J2-3207 Project: Log4j 2 Issue Type

[jira] [Commented] (LOG4J2-3297) Disable remote loading of log4j configuration to prevent MiTM Attacks

[ https://issues.apache.org/jira/browse/LOG4J2-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469438#comment-17469438 ] Brian Martin commented on LOG4J2-3297: -- To be clear, does Log4j load a remote confi