- doing integration tests with various databases for logback-access

- dropped retrotranslator support

Now, only Context's have a property map. A number of classes has to change to reflect this change.

- first-step to using JUnit 4.

see also http://mojo.codehaus.org/retrotranslator-maven-plugin/index.html

- updates to documentation
- replaced slf4j-api-1.4.0.jar with slf4j-api-1.4.3.jar

- removing logback-core/lib directory

- adding resource reading capability in IncludeFileAction (see bug 89)
  cleaning up IncludeFileActionTest.java
- other minor changes

- Preparing release 0.9.7.

[1] http://bugzilla.qos.ch/show_bug.cgi?id=75
[2] http://bugzilla.qos.ch/show_bug.cgi?id=76

- marking release 0.9.4
- a small improvement to ConverterTest

- starting work on 0.9.6-SNAPSHOT

reverting to previous config of retrotranslator plugin

Several dependencies are declared with scope=compile and optional=true.
When a user application depends only on lb-classic, only the classic, core and slf4j-api are packaged. Any other dependency
has to be managed by the user: logback does not include any other jars by itself.

The JKD1.4 jars are always created. By default, there is no verification.
When the "retrotranslator" profile is called, the verification is done. Thus, this
profile require the property path.to.rt.jar to be set.

Updated access' pom.xml with dependency to javax.mail

updates news page