A number of issues have comments here that they won't be fixed in 1.2.
Rather than just marking them to WONTFIX or closed wouldn't it be more
appropriate to create a corresponding issue in Jira (where appropriate)
for log4j2 so it can be considered?
[EMAIL PROTECTED] wrote:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43204
Thorbjørn Ravn Andersen <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #7 from Thorbjørn Ravn Andersen <[EMAIL PROTECTED]> 2008-08-02
13:27:00 PST ---
If this result in log4j requiring an 5+ JVM, I do not think it should go in the
1.2.x release as it would break backwards compatability.
I would also suggest using slf4j to do the logging with log4j as the backend as
it provides the delayed log string construction with {}-markers.
Hence I suggest this bug to be a WONTFIX.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
