[jira] [Commented] (LOG4J2-3031) Doc/Bug?/Feature: code configuration better

[ https://issues.apache.org/jira/browse/LOG4J2-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376545#comment-17376545 ] Caleb Cushing commented on LOG4J2-3031: --- Honestly I just gave up on it. Source diving when better

[jira] [Commented] (LOG4J2-3032) Memory appender that can be flushed to another appender later

[ https://issues.apache.org/jira/browse/LOG4J2-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293240#comment-17293240 ] Caleb Cushing commented on LOG4J2-3032: --- Yeah, looks like a duplicate. > Memory appender that can

[jira] [Commented] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293237#comment-17293237 ] Caleb Cushing commented on LOG4J2-3034: --- Wouldn't that change it for just 2 levels? I'm talking

[jira] [Updated] (LOG4J2-3034) Change Log format based on currently active level

[ https://issues.apache.org/jira/browse/LOG4J2-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-3034: -- Description: I'm not talking about `patternSelector`, I thought that was what I wanted, but I

[jira] [Created] (LOG4J2-3034) Change Log format based on currently active level

Caleb Cushing created LOG4J2-3034: - Summary: Change Log format based on currently active level Key: LOG4J2-3034 URL: https://issues.apache.org/jira/browse/LOG4J2-3034 Project: Log4j 2 Issue

[jira] [Created] (LOG4J2-3033) LogBuilder don't require a message

Caleb Cushing created LOG4J2-3033: - Summary: LogBuilder don't require a message Key: LOG4J2-3033 URL: https://issues.apache.org/jira/browse/LOG4J2-3033 Project: Log4j 2 Issue Type: New

[jira] [Created] (LOG4J2-3032) Memory appender that can be flushed to another appender later

Caleb Cushing created LOG4J2-3032: - Summary: Memory appender that can be flushed to another appender later Key: LOG4J2-3032 URL: https://issues.apache.org/jira/browse/LOG4J2-3032 Project: Log4j 2

[jira] [Updated] (LOG4J2-3031) Doc/Bug?/Feature: code configuration better

[ https://issues.apache.org/jira/browse/LOG4J2-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-3031: -- Description: I've had nothing but problems trying to get the code configuration working. I

[jira] [Created] (LOG4J2-3031) code configuration woes

Caleb Cushing created LOG4J2-3031: - Summary: code configuration woes Key: LOG4J2-3031 URL: https://issues.apache.org/jira/browse/LOG4J2-3031 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292459#comment-17292459 ] Caleb Cushing commented on LOG4J2-2971: --- I did work around it. > Level as Enum > - >

[jira] [Commented] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292458#comment-17292458 ] Caleb Cushing commented on LOG4J2-2971: --- The problem isn't that statement, it's that picocli is

[jira] [Commented] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17245880#comment-17245880 ] Caleb Cushing commented on LOG4J2-2971: --- hmm... but the only way to go from StandardLevel (which I

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Description: Tried to write this code with picocli only to be surprised when it didn't work.

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Description: I suspect this would be an API breaking change, but it seems like the `Level`

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Description: I suspect this would be an API breaking change, but it seems like the `Level`

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Description: I suspect this would be an API breaking change, but it seems like the `Level`

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Description: I suspect this would be an API breaking change, but it seems like the `Level`

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Description: I suspect this would be an API breaking change, but it seems like the `Level`

[jira] [Created] (LOG4J2-2971) Level as Enum

Caleb Cushing created LOG4J2-2971: - Summary: Level as Enum Key: LOG4J2-2971 URL: https://issues.apache.org/jira/browse/LOG4J2-2971 Project: Log4j 2 Issue Type: Bug Reporter:

[jira] [Updated] (LOG4J2-2971) Level as Enum

[ https://issues.apache.org/jira/browse/LOG4J2-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Cushing updated LOG4J2-2971: -- Issue Type: New Feature (was: Bug) > Level as Enum > - > > Key:

[jira] [Created] (LOG4J2-2372) Deduplication of messages

Caleb Cushing created LOG4J2-2372: - Summary: Deduplication of messages Key: LOG4J2-2372 URL: https://issues.apache.org/jira/browse/LOG4J2-2372 Project: Log4j 2 Issue Type: Improvement

[jira] [Created] (LOG4J2-2359) Safe multiline messages

Caleb Cushing created LOG4J2-2359: - Summary: Safe multiline messages Key: LOG4J2-2359 URL: https://issues.apache.org/jira/browse/LOG4J2-2359 Project: Log4j 2 Issue Type: Improvement

[jira] [Created] (LOG4J2-2356) A way to print just the stack trace in the message

Caleb Cushing created LOG4J2-2356: - Summary: A way to print just the stack trace in the message Key: LOG4J2-2356 URL: https://issues.apache.org/jira/browse/LOG4J2-2356 Project: Log4j 2 Issue