search

ops4j / org.ops4j.pax.logging

The OSGi Logging framework implementation. Supports SLF4J,LOG4J,JCL etc.
https://ops4j1.jira.com/wiki/spaces/paxlogging/overview
Apache License 2.0
46 stars 79 forks source link

Implement org.osgi.service.log.admin [PAXLOGGING-267] #336

Open ops4j-issues opened 5 years ago

ops4j-issues commented 5 years ago

Grzegorz Grzybek created PAXLOGGING-267

Fixed in: 2.0.7 Votes: 0, Watches: 1

ops4j-issues commented 4 years ago

Grzegorz Grzybek commented

https://issues.apache.org/jira/browse/KARAF-5559 changed Karaf's log:display command to change level of org.apache.sshd logger twice (which is understandable), but this leads to two reconfigurations of logging framework:

2020-01-27 07:43:44,891 INFO  {CM Configuration Updater (Update: pid=org.ops4j.pax.logging)} [org.ops4j.pax.logging.spi.support.EventAdminConfigurationNotifier.configurationDone()] (EventAdminConfigurationNotifier.java:48) : Sending Event Admin notification (configuration successful) to org/ops4j/pax/logging/Configuration
2020-01-27 07:43:44,919 INFO  {CM Configuration Updater (Update: pid=org.ops4j.pax.logging)} [org.ops4j.pax.logging.spi.support.EventAdminConfigurationNotifier.configurationDone()] (EventAdminConfigurationNotifier.java:48) : Sending Event Admin notification (configuration successful) to org/ops4j/pax/logging/Configuration

With org.osgi.service.log.admin implemented, we could change log:display command, so it can change level only without reconfiguration of entire logging framework.