[Fwd: Re: [vote] plans for turbine 2.3] A note from the turbine list about logging

Nicola Ken Barozzi <[email protected]>
Newsgroups gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel
Message-ID <[email protected]>

-------- Original Message --------
Subject: Re: [vote] plans for turbine 2.3
Date: 10 Dec 2002 20:15:27 -0500
From: James Taylor <[email protected]>
Reply-To: Turbine Developers List <[email protected]>
To: turbine-dev <[email protected]>
References: <BA1BD0EF.4724A%[email protected]>


> > Anyway, I will propose again to our list that we use the Logger
> > interface somehow in the new Avalon 5, or try somehow to reunite the scism.
> 
> +1
> 
> Avalon should drop whatever duplicate logging interfaces it has and adopt
> commons-logging. The same should go for Turbine and every other Jakarta
> application out there.

Agreed!

If I could implement LogEnabled, and have the logging facade provided by
the container be a commons-logging class, that would meet everyone's
needs I think. We could share the interfaces through commons, but choose
not to use the LogFactory class (and its associated discovery stuff) as
we wish.


-- 
Nicola Ken Barozzi                   [email protected]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.