- Added LogbackException (extending RuntimeException) 
- Added a throws "LogbackException" to Appender.doAppend method 

These changes allow "transactional" logback modules, e.g. logback-audit to 
throw exceptions. Other best-effort modules may catch LogbackExceptios effectively
hiding them from the user.

The autoConfig method in ContextInitializer class now throws a JoranException 

Fixing bug 70 involving the %throwable conversion word.

http://bugzilla.qos.ch/show_bug.cgi?id=70

http://bugzilla.qos.ch/show_bug.cgi?id=63

Fix for bug report 63.

Users can make call to log4j using log4j's TRACE level. TRACE is part 
of org.apache.log4j.Level and not o.a.l.Priority as it was introduced in
log4j 1.2.12.

See also http://bugzilla.qos.ch/show_bug.cgi?id=63

Added trace methods to syncing with SLF4J version 1.4.0

Fixed JMX related problem observed when running under JDK 1.4.

For more details please see:

  http://marc.info/?l=logback-user&m=117766102225897&w=2

depend on SLF4J 1.4.0-SNAPSHOT (not yet released)

No commit message

improved docs

SubTimeBasedRollingPolicy which was used to run the test faster has been deleted. Current time can now be set into TimeBasedRollingPolicy.

- starting work on 0.9.6-SNAPSHOT

- Contrary to previous versions of logback, the various
  Logger.isXYZEnabled(Marker) methods now take into account the marker
  information passed as parameter.

- Renamed LoggerTest as TurboFilteringInLoggerTest
- Fixed serious bugs in isXYZEnabled methods as reported in http://www.slf4j.org/pipermail/user/2007-April/000319.html

Renamed TimeBasedRollingPolicyTest to SubTimeBasedRollingPolicy so that it is not mistaken for a test case.

We call a subclass of TimeBasedRollingPolicy and inject time to trigger the rollover.