Add support for Log4j API and SLF4J #177
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The logging backends supported by the default
LogFactoryImpl
have all reached their end-of-life (except JUL andSimpleLog
). Third-generation logging backends, such as Log4j Core, support multiple logger contexts per application and therefore can not be handled by the simplified caching mechanism inLogFactoryImpl
.This PR introduces two new
LogFactory
implementations,Log4j2LogFactory
andSlf4jLogFactory
, that forward messages to the Log4j API and SLF4J respectively.During initialization the three existing factories are checked in the following order:
Log4j2LogFactory
has highest priority, since the Log4j API can faithfully transmit messages of typeObject
,Slf4jLogFactory
is the next choice. However, if the Log4j-to-SLF4J bridge is present we log directly to SLF4J instead of the Log4j API.LogFactoryImpl
has lowest priority.All the messages produced by loggers from
Log4j2LogFactory
andSlf4jLogFactory
are marked with aCOMMONS-LOGGING
marker.This PR also marks the old
Log4jLogger
class as deprecated.