Hi Mike and Kevin,
Spectacular job!  Thank you and kudos to you guys on being true to the
spirit of open source!

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Mike Schilli [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, July 11, 2002 3:45 AM
>To: [EMAIL PROTECTED]
>Subject: Perl port of log4j released
>
>Hi there, log4j guys,
>
>just wanted to let you know that Kevin Goess and I just released the
first
>version of our Perl port
>of your great log4j package. We've made sure that we're as close to the
>original implementation as
>possible. The project is still being enhanced, however the current
release
>is stable and has been
>released to CPAN.
>
>Would you mind putting our project on
>
>    http://jakarta.apache.org/log4j/docs/download.html
>
>where you list all the ports of log4j? That'd be great. Here's the
>announcement I just sent out --
>for you to check the details of the project (the README file mentioned
>below contains a informative
>tutorial on the port):
>
>The log4perl project team proudly announces:
>
>    ========================================
>    Log::Log4perl has been released to CPAN!
>    ========================================
>
>Log::Log4perl is a Perl port of the widely popular Log4j logging
package.
>
>This project has been a collaborative effort of Mike Schilli and Kevin
>Goess. Our project page with the latest news and the latest CVS tree
can
>be viewed at
>
>    log4perl.sourceforge.net
>
>Wonder why you should use it? Logging beats a debugger when you want to
>know what's going on in your code during runtime. However, traditional
>logging packages are too static and generate a flood of log messages in
>your log files that won't help you.
>
>Log::Log4perl is different. It allows you to control the amount of
>logging messages generated very effectively. You can bump up the
logging
>level of certain components in your software, using powerful
inheritance
>techniques. You can redirect the additional logging messages to an
>entirely different output (append to a file, send by email etc.) -- and
>everything without modifying a single line of source code.
>
>Log::Log4perl very closely mimics the Java implementation (log4j) of
this
>logging engine -- we've gone a long way to make sure it can even
>read existing log4j configuration files and apply them to Perl
>without any problems!
>
>See how it works by reading this tutorial:
>    http://perlmeister.com/devel/Log-Log4perl/README
>
>Download the newest distribution:
>    http://perlmeister.com/devel/Log-Log4perl-0.16.tar.gz
>
>Get it from CPAN once the upload is complete:
>    $CPAN/authors/id/M/MS/MSCHILLI/Log-Log4perl-0.16.tar.gz
>
>Keep on logging!
>
>-- Mike
>--------------------------------------------------------
>Mike Schilli [EMAIL PROTECTED] http://perlmeister.com
>--------------------------------------------------------
>
>--
>To unsubscribe, e-mail:   <mailto:log4j-user-
>[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:log4j-user-
>[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to