[
https://issues.jboss.org/browse/JBLOGGING-95?page=com.atlassian.jira.plug...
]
Nicholas Williams commented on JBLOGGING-95:
--------------------------------------------
...that's not how Java works. They are absolutely in the same package, and it will
absolutely work.
Log4j 2 does exactly what I'm describing to support SLF4J:
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/slf4j-impl/src/ma...
My comment wasn't asking "will it work," because I know absolutely that it
will. My comment was asking whether it was acceptable to the dev team here to have code in
JBoss Logging (a single class) that was in the {{org.apache.logging.log4j.spi}} package.
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
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