> (Maybe I should stop yammering on general@) If it was our "commons" "general" problem, I would have already placed that Velocity stuff on the wrappers I stole from Avalon!
ARGH! Paulo > -----Original Message----- > From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 08, 2002 4:33 AM > To: Jakarta Commons Developers List > > > On 1/7/02 8:38 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote: > > >> Trying to build logging-package-specific knowledge like this > into a "thin" > >> wrapper layer seems like a slippery slope. > > > > For simple file based logging configuration it is actually quite simple > > to do that for the 3 logging APIs we have been talking about. > Very light. > > > > You can have a several modes: > > - Give me some already configured logger (minimal common logging code): > > - Find some logger already configured (just a bit more code); > > - Configure the logger you find to log to this file (just a bit more); > > > > - Primordial logger and silly simple logger would take more than the > > previous 2 bits. > > > > You can find some "log to this file" configuration code in Velocity for > > both Log4J and LogKit. You can find it at: > > CVS Repository: > > jakarta-velocity > > path: > > \src\java\org\apache\velocity\runtime\log > > > > I have been wanting to jump into this thread and mention it, but I am so > hopelessly behind I can never seem to catch up. > > (Maybe I should stop yammering on general@) > > Yes, this system seems to work well for us, basically finding the first > supported logging system in the classpath if no logger is > configured by the > application. > > -- > Geir Magnusson Jr. [EMAIL PROTECTED] > System and Software Consulting > You're going to end up getting pissed at your software > anyway, so you might as well not pay for it. Try Open Source. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
