Page Comparison

Wiki Markup
{zone-template-instance:Template-Release-1.4}
{zone-data:version}1.56.0{zone-data}
{zone-data:releaseDate}MayJanuary 426, 20102011{zone-data}
{zone-data:overview}
This is mainly a maintenance release of Pax Logging. See the release notes below for details.
{zone-data:overview}
{zone-data}
{zone-data:releaseNotes}
h4. Release Notes - Pax Logging - Version 1.56.0

* BugNew    Feature
** [PAXLOGGING-5393|http://issues.ops4j.org/jira/browse/PAXLOGGING-5393] - IfSupports wemultiple use the LogReaderService all OSGI framework events duplicated.
    ** [PAXLOGGING-62|http://issues.ops4j.org/jira/browse/PAXLOGGING-62] - DefaultServiceLog.level WARNING is not recognized
    ** [PAXLOGGING-65|http://issues.ops4j.org/jira/browse/PAXLOGGING-65] - JCL LogFactory.FACTORY_DEFAULT points to non-existent LogFactory implementation
    ** [PAXLOGGING-66|http://issues.ops4j.org/jira/browse/PAXLOGGING-66] - NPE in JULI LogFactory
    ** [PAXLOGGING-67|http://issues.ops4j.org/jira/browse/PAXLOGGING-67] - versions in poms are messed up, so trunk won't build
    ** [PAXLOGGING-70|http://issues.ops4j.org/jira/browse/PAXLOGGING-70] - NPE When using anonymous logger from java.util.logging
    ** [PAXLOGGING-73|http://issues.ops4j.org/jira/browse/PAXLOGGING-73] - Java Util Logging is always sent to console
    ** [PAXLOGGING-74|http://issues.ops4j.org/jira/browse/PAXLOGGING-74] - Logger.isEnabledFor(Priority) is bugged
    ** [PAXLOGGING-81|http://issues.ops4j.org/jira/browse/PAXLOGGING-81] - The default log level is not used anymore
    ** [PAXLOGGING-82|http://issues.ops4j.org/jira/browse/PAXLOGGING-82] - When the configuration is updated, the hierarchy is not reset to defaults before the reconfiguration

* Improvement
    osgi appenders in the configuration by using a ldap filter
** [PAXLOGGING-6391|http://issues.ops4j.org/jira/browse/PAXLOGGING-6391] - RenameUse internal package in pax-logging-service
    ** [PAXLOGGING-69|http://issues.ops4j.org/jira/browse/PAXLOGGING-69] - IDEA project files are in svn, and module directory and names don't match
    ** [PAXLOGGING-77|http://issues.ops4j.org/jira/browse/PAXLOGGING-77] - Upgrade to Log4j 1.2.16 
    ** [PAXLOGGING-79|http://issues.ops4j.org/jira/browse/PAXLOGGING-79] - Read property for disabling JUL from bundle context

* New Feature
    ** [PAXLOGGING-64|http://issues.ops4j.org/jira/browse/PAXLOGGING-64] - Property to switch on/off fallback buffering log
    ** [PAXLOGGING-76|http://issues.ops4j.org/jira/browse/PAXLOGGING-76] - Support for filters, error handlers and nested appenders
    ** [PAXLOGGING-78|http://issues.ops4j.org/jira/browse/PAXLOGGING-78] - Have the bundle issuing the log event be available on all events
    ** [PAXLOGGING-80|http://issues.ops4j.org/jira/browse/PAXLOGGING-80] - Add an OSGi enhanced throwable rendered to indicate bundle information in the stack trace
    ** [PAXLOGGING-83|http://issues.ops4j.org/jira/browse/PAXLOGGING-83] - Enhance log4j to be able to have a split appender based on MDC context attributes
SLF4J 1.6.1 API
{zone-data}
{zone-template-instance}
Versions Compared

Old Version 2

New Version 3

Key
