Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{excerpt:hidden=true}Details about what is changed in each release{excerpt}

{ops4j-style-page}

{anchor:1.3.0}
h4. Release Notes - Pax Logging - Version 1.3.0 (January 13, 2009)
* Bug
** [PAXLOGGING-31|http://issues.ops4j.org/jira/browse/PAXLOGGING-31] - Pax Logging unusable with SpringSecurity 2.0.2.A
** [PAXLOGGING-34|http://issues.ops4j.org/jira/browse/PAXLOGGING-34] - Configuration of Log4j Delegate Within PaxLoggingServiceImpl Varies During Startup
** [PAXLOGGING-41|http://issues.ops4j.org/jira/browse/PAXLOGGING-41] - NPE thrown when message is null
** [PAXLOGGING-43|http://issues.ops4j.org/jira/browse/PAXLOGGING-43] - Incomplete SLF4J Marker Support
** [PAXLOGGING-44|http://issues.ops4j.org/jira/browse/PAXLOGGING-44] - java.util.ConcurrentModificationException ERROR on Pax-Logging-API
** [PAXLOGGING-46|http://issues.ops4j.org/jira/browse/PAXLOGGING-46] - Log4j Category uses reference comparison when checking priorities and levels
** [PAXLOGGING-47|http://issues.ops4j.org/jira/browse/PAXLOGGING-47] - PaxLogging ends up in cyclic loop on WebSphere server
* Improvement
** [PAXLOGGING-35|http://issues.ops4j.org/jira/browse/PAXLOGGING-35] - Add support for MDC style PaxContext With Adjunct Support for log4j and slf4j MDC
** [PAXLOGGING-40|http://issues.ops4j.org/jira/browse/PAXLOGGING-40] - Upgrade to SLF4J latest api (1.5.6)

{anchor:1.2.1}
h4. Release Notes - Pax Logging - Version 1.2.1 (November 17, 2008)
* Improvement
** [PAXLOGGING-42|http://issues.ops4j.org/jira/browse/PAXLOGGING-42] - Implement org.apache.log4j.Category.isEnabledFor(Level)

{anchor:1.2.0}
h4. Release Notes - Pax Logging - Version 1.2.0 (November 13, 2008)
* Bug
** [PAXLOGGING-38|http://issues.ops4j.org/jira/browse/PAXLOGGING-38] - pax-logging-service bundle is missing org.apache.log4j.net package
* Improvement
** [PAXLOGGING-37|http://issues.ops4j.org/jira/browse/PAXLOGGING-37] - Make the level of the log events in FrameworkHandler configurable and defaulted to DEBUG

{anchor:1.1.1}
h4. Release Notes - Pax Logging - Version 1.1.1 (May 30, 2008)
* Bug
** [PAXLOGGING-28|http://issues.ops4j.org/jira/browse/PAXLOGGING-28] - Pax-Logging unusable with Spring 2.5.4.A
** [PAXLOGGING-29|http://issues.ops4j.org/jira/browse/PAXLOGGING-29] - java.lang.NullPointerException on java.util.LinkedList.remove
* Improvement
** [PAXLOGGING-23|http://issues.ops4j.org/jira/browse/PAXLOGGING-23] - Handle configuration removal

{anchor:1.0.0}
h4. Release Notes - Pax Logging - Version 1.0.0 (January 31, 2008)
* Bug
** [ops4j:PAXLOGGING-19] - Legacy log API calls generate Event Admin events only for trace
** [ops4j:PAXLOGGING-21] - Malformed log messages with slf4j
** [ops4j:PAXLOGGING-25] - pax-logging throws a NPE while trying to log
* Task
** [ops4j:PAXLOGGING-14] - Pax Logging need to pass OSGi TCK