On Apr 7, 2017 5:58 AM, "Neil Bartlett" <[email protected]> wrote:
The draft specification repeatedly mentions SLF4J and supports it explicitly. Log4j is an implementation that can be used behind SLF4J. So… what’s missing? I have some actual comments (from RFC) 1. Deprecation annotations on LogListener and LogReaderService (also class @Deprecated on LogService). 2. Marker interface (and appropriate methods on Logger) 3. On Logger, add generic isEnabled(LogLevel) and log(LogLevel, Blah blah) methods. Hate that this isn't exposed by slf4j api. 4. Allow non-fqdn Logger names. Could support hierarchy, or could force parent to ROOT. 5. Allow Loggers to be selected using a filter. 6. Provide specification for pre-bundle logging for frameworks. (maybe) Simon P.S. Any estimate of what percentage of hosted fragments are guests of slf4j?
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
