On Thu, Aug 9, 2012 at 4:32 PM, Ralph Goers wrote:
> This topic has come up several times, although your request seems slightly
> different.
>
> Every log event in Log4j 2 is handled by a message object. When you specify
> logger.debug("", p1, p2) that gets converted essentially to logger.debug
Ralph Goers created LOG4J2-67:
-
Summary: Allow plugins outside of Log4j 2 core to be preloaded.
Key: LOG4J2-67
URL: https://issues.apache.org/jira/browse/LOG4J2-67
Project: Log4j 2
Issue Type: Ne
This topic has come up several times, although your request seems slightly
different.
Every log event in Log4j 2 is handled by a message object. When you specify
logger.debug("", p1, p2) that gets converted essentially to logger.debug(new
ParameterizedMessage("", p1, p2)); . So if you want t
Forgive me if this feature already exists, but I was hoping to find if
log4j 2 contained a way to configure the format *provider* of
parametrized messages. This is an important aspect for my own work
because I have some sophisticated formatting in my logs that use
String.format() [1] -- especially
[
https://issues.apache.org/jira/browse/LOG4J2-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432042#comment-13432042
]
Paul Benedict commented on LOG4J2-66:
-
In addition, the source folder should probably i
Paul Benedict created LOG4J2-66:
---
Summary: Binary package does not include "apache" name in root
directory
Key: LOG4J2-66
URL: https://issues.apache.org/jira/browse/LOG4J2-66
Project: Log4j 2
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-chainsaw has an issue affecting its community integration.
T
[
https://issues.apache.org/jira/browse/LOG4J2-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Anev closed LOG4J2-64.
---
> Log4j 2 is not working with JDK 1.7
> ---
>
> Key: LOG4J2-64
