logback-access uses it as well.
  
- Added unit tests in relation with default component class mapping rules in Joran. 
  See also jira issue LBCLASSIC-103

Related to LBCORE-83.
 

- Added StatusMessage viewer servlet for lb-classic called ViewStatusMessagesServlet. 

- Added StatusMessage viewer servlet for lb-access called ViewStatusMessagesServlet. 
  It works with Tomcat but not Jetty.

- Added relevant documentation.

- Fix LBCORE-74
  
  HTMLLayoutBase now takes into custom conversion words.
  
- Moved StringListAppender to c.q.l.classic.testUtil package

- cleaned up config files so that "level" is an XML attribute and not
  an XML element

- updated Gmail related examples

- LBCLASSIC-100

  Evaluators are now wired into an appender automatically (implicit
  rules) without the help of EvaluatorAction. EvaluatorAction is now
  only needed for global evaluator elements.

  It follows that name attribute is necessary only for global
  evaluators. Embedded evaluators no longer need a name.

  EvaluatorAction has been modified to accept evaluators of any type
  and not just JaninoEvaluators.

- add tests for verifying that parameter types which are concrete classes 
  can be instantiated by implicit actions
- ongoing work on evaluators

  Thus, it is no longer necessary to specify the class name as an xml attribute for sub-components
  
- refactoring of sibling appender 

- logback-access tests are now all JUnit4

 - Absorb thrown SecurityException/AccessControlException when accessing system properties
   This fixes LBCLASSIC-86

run on older JDKs we make JDK 1.6 a requirement for running the DBAppenderIntegration tests. 

We now use sqljdbc4. (note the suffix 4)

  between successive runs

This should make the code a somewhat clearer

Given dependencies on test-jar logback could not be build as 'mvn package' from 
a pristine local repository. One had to 'mvn install' first. 

- doing integration tests with various databases for logback-access