You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Geir Magnusson Jr." <ge...@optonline.net> on 2002/01/08 04:32:53 UTC
Re: cvs commit:
jakarta-commons/logging/src/java/org/apache/commons/logging Jdk14Logger.java
LogSource.java package.html
On 1/7/02 8:38 PM, "Paulo Gaspar" <pa...@krankikom.de> 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. geirm@optonline.net
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: cvs commit:jakarta-commons/logging/src/java/org/apache/commons/logging Jdk14Logger.java LogSource.java package.html
Posted by Paulo Gaspar <pa...@krankikom.de>.
> (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:geirm@optonline.net]
> Sent: Tuesday, January 08, 2002 4:33 AM
> To: Jakarta Commons Developers List
>
>
> On 1/7/02 8:38 PM, "Paulo Gaspar" <pa...@krankikom.de> 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. geirm@optonline.net
> 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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>