to a single implementation of my own choice.
>>
>> I see there is a way to make Log4j2 an SLF4J implementation, but I could not
>> see any documentation on redirecting Log4j2 to SLF4J in the event that the
>> end application does not wish to use Log4j2 as its logging implenta
ients to
> use its API directly, making SLF4J the simplest means for centralising the
> diverse logging APIs in use to a single implementation of my own choice.
>
> I see there is a way to make Log4j2 an SLF4J implementation, but I could not
> see any documentation on redirecting Log4j
; diverse logging APIs in use to a single implementation of my own choice.
>
> I see there is a way to make Log4j2 an SLF4J implementation, but I could not
> see any documentation on redirecting Log4j2 to SLF4J in the event that the
> end application does not wish to use Log4j2 as it
implementation, but I could not
see any documentation on redirecting Log4j2 to SLF4J in the event that the end
application does not wish to use Log4j2 as its logging implentation. Is this on
the cards?
Thanks,
Rob
-
To unsub
