[
https://issues.jboss.org/browse/JBLOGGING-95?page=com.atlassian.jira.plug...
]
Nicholas Williams edited comment on JBLOGGING-95 at 2/2/14 2:46 PM:
--------------------------------------------------------------------
Huh. I didn't even notice that this had been merged and close. Guess I didn't get
the email update or something. Thanks!
Since this didn't get backported and included in 3.1.4.GA (sad face), when do we
expect 3.2.0 to come out? Log4j 2 is going GA in the next couple of weeks, my book goes to
the printers next week, and I'd really like this to all line up. I'd at least like
to get 3.2.0.Beta1 rolling in the next week or two. There haven't been many changes at
all to this version. :-)
Is there anything I can do to help move things along?
was (Author: beamerblvd):
Huh. I didn't even notice that this had been merged and close. Guess I didn't
get the email update or something. Thanks!
Since this didn't get backported and included in 3.1.4.GA (sad face), when do we
expect 3.2.0 to come out? Log4j 2 is going GA in the next couple of weeks, my book goes to
the printers next week, and I'd really like this to all line up. :-)
Is there anything I can do to help move things along?
Add Logger/LoggerProvider to support new Log4j 2 to improve
performance
-----------------------------------------------------------------------
Key: JBLOGGING-95
URL:
https://issues.jboss.org/browse/JBLOGGING-95
Project: JBoss Logging
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: jboss-logging-spi
Affects Versions: 3.2.0.Beta1
Reporter: Nicholas Williams
Assignee: David Lloyd
Priority: Minor
Fix For: 3.2.0.Beta1
Original Estimate: 1 day
Remaining Estimate: 1 day
The new Log4j 2 project will be released soon. It has major improvements over Log4j and
Logback. Currently, JBoss Logging can log to Log4j 2 indirectly by way of SLF4J (if the
log4j-slf4j artifact is on the classpath) or the Log4j 1.2 API (if the log4j-1.2-api
artifact is on the classpath and when JBLOGGING-94 is fixed). However, performance would
be improved if JBoss Logging could log directly to the Log4j 2 API.
Looks like we just need a new {{Log4j2Logger}} and {{Log4j2LoggerProvider}}. I'll try
to submit a pull request in the next few weeks. I'm currently working on other tasks
in Log4j 2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira