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

- We now avoid polluting the output with image contents which most of the time look like gibberish anyhow.

Significantly more robust TeeFilter. This version does not barf
 - on images, css files etc.
 - application/x-www-form-urlencoded requests
 
 If the request is application/x-www-form-urlencoded, TeeFilter attempts to recreate the input 
 altough it might be able to do so only approximately

reverting to previous config of retrotranslator plugin

Minor fixes

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.

Slight CSS modification

  This requires adding a special filter (TeeFilter.java)

- Added FullRequestConverter.java which outputs the full contents of the request including request payload

- Minor changes to PatternLayout (DOC NEEDS TO BE UPDATED)
- Renaming changes in AccessEvent.java

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.