FileAppender will now automatically create parent directories as needed.

- added unit tests 
- updated the documentation

- Allow TimeBasedRollingPolicy to delete old files if asked by the user.
- PeriodicityType are now listed in an enum.

- renamed ClassPackagingDataCalculator as PackagingDataCalculator
- added calculatePackagingData method to ThrowableProxy so that converters can
  force calculation of packaging data
- added relevant test cases

Increase slack factor to 8 for Sun's JDK 1.6. For some reason, slack factor of 6 for JDK 1.5 was insufficient.

- improved "demo" page
- Sync with SLF4J (1.5.3)

Class packaging information is now automatically added to stack traces formatted by PatternLayout

Not using Geronimo JMS instead of Sun JMS to avoid manual installation

this change reduces the probability of that happening

This code attempts to guarantee that the extracted class packaging information 
is extracting using the *exact* same classloader was used to load a given class
in the stack frame. 

Associated test cases. 

 	 
 	 Working on the reliability of the extracted package information which is actually quite a difficult problem.

Reworking Throwable to string conversion. Instead of simply converting StackTraceElement 
(STE) array into just strings, we convert them to a little more sophisticated objects,
namely ThrowableDataPoints which support PackageInformation.

All tests pass.

Reworking Throwable to string conversion. Instead of simply converting StackTraceElement 
(STE) array into just strings, we convert them to a little more sophisticated objects,
namely ThrowableDataPoints which support PackageInformation.

This is ongoing work, unit test may not pass. 

  
  Unfortunately, this implementations fails the Scenario unit tests. Yes, it looks 
  like a JDK bug (very suprisingly).
  
  Commiting this version for historical (archiving) purposes.

Extracting package information is a time consuming process. 
Improve performance by keeping previously found results in a cache.
Added an LRUCache with accompanying test cases for this purpose. 

The c.q.l.core.util.Loader class is used to load classes or locate resources. 
Previously, the TCCL (Thread Context Class Loader) was used to locate resources,
in particular configuration files. However, the TCCL is not set in all environments. 

Instead of using the TCL use now use the class loader that loaded the Loader class
itself to load resources. Now, under many circumstances TCCL==self classloader
so most users will not see a difference. The situation where TCCL != self cl
can occur under relatively complicated scenarios. Thus, this commit simplifies the code
without hopefully affecting existing deployments. 

added a small ant script to automatically copy slf4j-api-${VERSION}.jar to lib/