3.0.0-beta1

This release constitutes a major rework of the initial release.
Since the Tomcat Log4j Core lookup and Tomcat Classloader need to be in different classloaders, the log4j-tomcat is split in two parts:

• the Tomcat Lookup is left in the log4j-tomcat artifact.
• the Tomcat classloaders are moved to a new tomcat-log4j artifact.

New components

The set of tools to integrate Log4j and Tomcat is expanded to include:

• a new Tomcat JULI to Log4j API bridge.
• two Tomcat context selectors.
• a Tomcat context data provider.

Added

• Add parallel version of Log4jWebappClassLoader. (#46)

Changed

• Add Tomcat JULI implementation in artifact tomcat-juli-to-log4j. (#101)
• Add a context data provider to fill the "engine.name", "host.name" and "context.name" context entries. (#103)
• Add context selector based on Tomcat's thread context classloaders. (#105)
• Split Tomcat classloaders into a new tomcat-log4j artifact. (#80)

2.18.0

First release containing:

• a Tomcat classloader that applies the "delegate to parent first" strategy to log4j-api classes,
• a Log4j Core lookup that resolves the name of the application currently running on the thread.