Stephen, > I added the following to the logger compile target: > > <exclude name="**/LF5TargetFactory.java*" > unless="log4j.present"/>
I'm not sure this solves the big picture problem. Upon further reflection, it seems to me that the issue occurs when an older version of the log4j binary is present in the Avalon-logkit build. In this case the Avalon-logkit build acts as if log4j is present, and tries to compile the log4j files, including LF5TargetFactory. Log4j.present is set based on a class present in older versions of Log4j (those that don't contain the required LF5 classes) and hence compilation fails. Note that it is this problem that cascades to cause the Excalibur-logger failure that was reported by Gump last night. --Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
