Peter Donald wrote: > > At 09:07 8/5/01 -0000, [EMAIL PROTECTED] wrote: > >bloritsch 01/05/08 14:07:37 > > > > Added: lib avalon-framework.jar > > Log: > > Add ability to print cascading exceptions. This implementation does not > require > > Avalon Framework in the distributed jar--just the compile. It tests the > exception to > > see if it is an instance of CascadingThrowable. If not, everything acts > as it has in > > the past. If so, then we recursively call the method until there are no > more > > CascadingThrowable. > > -1 on this change as Avalon *will* be required at runtime. The reason is > that PatternFormatter will not resolve without AvalonFramework present and > as almost all users of Logkit use PatternFormatter (as it is default > formatter).
Crap. I *know* there has to be some kind of black magic.... OK. Can we have the AvalonLogFormatter in LogKit. If the jar exists, that class gets compiled--otherwise the ability of LogKit is crippled. I think that would help the most people involved--without penalizing people who just use LogKit. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
