log4perl-devel

RE: [log4perl-devel] log4perl and log4j

[Viner, D. <dv...@ya...>]

I'll look into what it takes to get info on logging.apache.org.  

what do you think about a couple of compatibility functions to support the
identical syntax ? e.g., :

sub isDebugEnabled { return shift->is_debug(); }


dave

-----Original Message-----
From: Mike Schilli [mailto:b2...@pe...] 
Sent: Sunday, March 28, 2004 1:20 AM
To: Viner David
Cc: Log4perl-Devel (log...@li...)
Subject: Re: [log4perl-devel] log4perl and log4j


Viner, David wrote on 3/26/2004, 10:59 AM:

 > I noticed in reading about log4j that it exposes slightly different
 > method
 > names than log4perl. for example,
 >
 > log4perl: is_debug()    log4j:  isDebugEnabled()
 > log4perl: is_info()     log4j:  isInfoEnabled()
 > log4perl: is_warn()     log4j:  _none_
 > log4perl: is_error()    log4j:  _none_
 > log4perl: is_fatal()    log4j:  _none_

The overall l4p goal is to be compatible with log4j, but there's some 
minor differences, especially when there's more perlish ways. The 
underscore notation vs. upper/lowercasing is something we used 
throughout l4p.

 > Also, we should look into how to get log4perl listed and linked to on
 > http://logging.apache.org/
 > Thoughts?

I got an invite on this, but I passed -- sounds like a lot of work. Are 
you volunteering?

-- 
-- Mike
Mike Schilli
m...@pe...

RE: [log4perl-devel] log4perl and log4j

[Viner, D. <dv...@ya...>]

After talking more with the ASF team that owns logging.apache.org, it seems
as tho licensing issues will prevent integration. Specifically, the Logging
Services at ASF requires that software be licensed with the Apache Software
License or ASL-compatible license.  At this time, it is unclear whether GPL
is compatible.  (GNU has declared it incompatible, but the ASF team is
discussing it with GNU team since the interpretation is uncertain.)
Moreover, the Apache Software Foundation does not allow double-licensing
which Log4Perl currently has (Artistic License and GPL).

I've asked them to put a link to the Log4Perl homepage on the
http://logging.apache.org site, and they have agreed.

Mike and Kevin, if you are willing or interested in changing the license
terms, please let me know.  Otherwise, we'll just keep pace with the logging
services on an unofficial basis.


dave

-----Original Message-----
From: Viner, David [mailto:dv...@ya...] 
Sent: Monday, March 29, 2004 10:14 AM
To: Log4perl-Devel (log...@li...)
Subject: RE: [log4perl-devel] log4perl and log4j


I'll look into what it takes to get info on logging.apache.org.  

what do you think about a couple of compatibility functions to support the
identical syntax ? e.g., :

sub isDebugEnabled { return shift->is_debug(); }


dave

-----Original Message-----
From: Mike Schilli [mailto:b2...@pe...] 
Sent: Sunday, March 28, 2004 1:20 AM
To: Viner David
Cc: Log4perl-Devel (log...@li...)
Subject: Re: [log4perl-devel] log4perl and log4j


Viner, David wrote on 3/26/2004, 10:59 AM:

 > I noticed in reading about log4j that it exposes slightly different
 > method
 > names than log4perl. for example,
 >
 > log4perl: is_debug()    log4j:  isDebugEnabled()
 > log4perl: is_info()     log4j:  isInfoEnabled()
 > log4perl: is_warn()     log4j:  _none_
 > log4perl: is_error()    log4j:  _none_
 > log4perl: is_fatal()    log4j:  _none_

The overall l4p goal is to be compatible with log4j, but there's some 
minor differences, especially when there's more perlish ways. The 
underscore notation vs. upper/lowercasing is something we used 
throughout l4p.

 > Also, we should look into how to get log4perl listed and linked to on
 > http://logging.apache.org/
 > Thoughts?

I got an invite on this, but I passed -- sounds like a lot of work. Are 
you volunteering?

-- 
-- Mike
Mike Schilli
m...@pe...



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
log4perl-devel mailing list
log...@li...
https://lists.sourceforge.net/lists/listinfo/log4perl-devel

RE: [log4perl-devel] log4perl and log4j

[Mike S. <m...@pe...>]

Viner, David wrote on 4/5/2004, 10:08 AM:

 > Mike and Kevin, if you are willing or interested in changing the license
 > terms, please let me know.  Otherwise, we'll just keep pace with the
 > logging
 > services on an unofficial basis.

As far as I'm concerned, I'm OK with the status quo for now -- if 
there's a significant gain from changing licenses, then we can certainly 
talk about it.

--
-- Mike
Mike Schilli
m...@pe...

RE: [log4perl-devel] log4perl and log4j

[Mike S. <m...@pe...>]

Viner, David wrote on 4/5/2004, 10:08 AM:

 > Mike and Kevin, if you are willing or interested in changing the license
 > terms, please let me know.  Otherwise, we'll just keep pace with the
 > logging
 > services on an unofficial basis.

... oh, and I forgot to add: Thanks for investigating this, Dave, we do 
apprechiate it, no matter which way we go.

--
-- Mike
Mike Schilli
m...@pe...

RE: [log4perl-devel] log4perl and log4j

[Viner, D. <dv...@ya...>]

Here's a patch including documentation for adding the is<Level>Enabled()
methods to log4perl.  These are the standard Log4x style of method naming...
so this is really just for compatibility.

I've also attached a simple test case to ensure that the isXxxEnabled() and
is_xxx() methods return the same value. 048Log4J-compat.t should live under
the t/ subdir.  (I couldn't seem to get cvs diff to do that for me... is
there some secret that I am missing? cvs diff -N seems like it should do it,
but somehow it just doesn't)

thanks
dave


-----Original Message-----
From: Mike Schilli [mailto:m...@pe...] 
Sent: Monday, March 29, 2004 3:57 PM
To: Viner David
Subject: RE: [log4perl-devel] log4perl and log4j


Viner, David wrote on 3/29/2004, 10:14 AM:

 > what do you think about a couple of compatibility functions to support
 > the
 > identical syntax ? e.g., :
 >
 > sub isDebugEnabled { return shift->is_debug(); }

Sure. Patches including test cases and documentation are welcome.

--
-- Mike
Mike Schilli
m...@pe...

RE: [log4perl-devel] log4perl and log4j

[Mike S. <m...@pe...>]

Viner, David wrote on 6/10/2004, 11:46 AM:

 > Here's a patch including documentation for adding the is<Level>Enabled()

Applied with shortened doc. I left out the test case, since these are 
just aliases. Thanks!

--
-- Mike
Mike Schilli
m...@pe...