Pax Logging - 1.5.0
Unknown macro: {zone-template-instance}
Unknown macro: {zone-data}
1.5.0
Unknown macro: {zone-data}
May 4, 2010
Unknown macro: {zone-data}
This is mainly a maintenance release of Pax Logging. See the release notes below for details.
Unknown macro: {zone-data}
Unknown macro: {zone-data}
Release Notes - Pax Logging - Version 1.5.0
- Bug
- PAXLOGGING-53 - If we use the LogReaderService all OSGI framework events duplicated.
- PAXLOGGING-62 - DefaultServiceLog.level WARNING is not recognized
- PAXLOGGING-65 - JCL LogFactory.FACTORY_DEFAULT points to non-existent LogFactory implementation
- PAXLOGGING-66 - NPE in JULI LogFactory
- PAXLOGGING-67 - versions in poms are messed up, so trunk won't build
- PAXLOGGING-70 - NPE When using anonymous logger from java.util.logging
- PAXLOGGING-73 - Java Util Logging is always sent to console
- PAXLOGGING-74 - Logger.isEnabledFor(Priority) is bugged
- PAXLOGGING-81 - The default log level is not used anymore
- PAXLOGGING-82 - When the configuration is updated, the hierarchy is not reset to defaults before the reconfiguration
- Improvement
- PAXLOGGING-63 - Rename internal package in pax-logging-service
- PAXLOGGING-69 - IDEA project files are in svn, and module directory and names don't match
- PAXLOGGING-77 - Upgrade to Log4j 1.2.16
- PAXLOGGING-79 - Read property for disabling JUL from bundle context
- New Feature
- PAXLOGGING-64 - Property to switch on/off fallback buffering log
- PAXLOGGING-76 - Support for filters, error handlers and nested appenders
- PAXLOGGING-78 - Have the bundle issuing the log event be available on all events
- PAXLOGGING-80 - Add an OSGi enhanced throwable rendered to indicate bundle information in the stack trace
- PAXLOGGING-83 - Enhance log4j to be able to have a split appender based on MDC context attributes