other modules, i.e. logback-classic

- FruitShell code is intended to test Joran's replay capability. 
  Thus the various config files have been moved under src/test/input/joran/replay
  

  It's static methods have become instance methods with their 
  first argument (a LoggerContext) removed. This leads to very slightly
  simpler code.

- added chapter numbering by CSS (firefox only)

- simplification of LoggerStatusPrinter
- improvements to documentation

Given that GPL+classpath exception is rejected in the same way as LGPL
by those requesting for a licensing change, there is no need for
change if the end result is the same.

- unit testing addition of status listener by logback.statusListenerClass system property

- Setting the logback.statusListenerClass system property to the name of a StatusListener 
  class will automatically instantiate an instance of that class and register will the 
  StatusManager currently in use by the logger context. By convention, SYSOUT represents 
  a shorthand for ch.qos.logback.core.status.OnConsoleStatusListener

- documentation to follow

ongoing work on StatusListner support

test case for StatusListner support 

Fixed synchronization problems. The iterator() method has been removed from 
the StatusManager interface. It has been replaced by getCopyOfStatusList
which, as the name indicates, returns a copy of the statusList contained in
the StatusManager instance. This avoids concurrency problems encountered
when the developer forget to synchronize on the statusManager before iterating
on its status list. 

Added a listener interface to status manager as suggested in LBCLASSIC-59 
by Anton Tagunov. 

Support for status listeners in Joran is still missing.

  host CPU

  under the target directory. See also http://www.qos.ch/pipermail/logback-dev/2008-July/002610.html
- logback now depends on slf4j version 5.1.3-snapshot
- lb-examples depends on slf4j-ext

- Related to LBCORE-32

  added support for passing the configuration file as a system property.
  The system property name is "logback.configurationFile". Values can be 
  of type URL, a file, or a resource name.

  I am guessing that this modification should satisfy the requirements
  for most users who voted on this issue. I am not too keen on adding
  other config directives as system properties as suggested by M. Fowles.