On Fri, 28 Dec 2001, Torsten Curdt wrote:
> > > > > > > Is the LOgKitManagement able to handle LogEnabled components?
> > > >
> > > > LogKitManager itself is LogEnabled. but It manage org.apache.log.Logger.
> > > > It depend of LogKit.
> > > [snip]
> > > > > > Well, I assumed - since Loggable got
> > > > > > Is the LOgKitManagement able to handle LogEnabled components?
> > >
> > > LogKitManager itself is LogEnabled. but It manage org.apache.log.Logger.
> > > It depend of LogKit.
> > [snip]
> > > > > Well, I assumed - since Loggable got deprecated... (I thought _you_
> > > > > would be the
On Sat, 22 Dec 2001, Torsten Curdt wrote:
> > > > > > I volunteer to do it...
> > > > >
> > > > > Is the LOgKitManagement able to handle LogEnabled components?
> >
> > LogKitManager itself is LogEnabled. but It manage org.apache.log.Logger.
> > It depend of LogKit.
> [snip]
> > > > Well, I assume
On Sat, 22 Dec 2001, Eung-ju Park wrote:
>
> - Original Message -
> From: "giacomo" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, December 21, 2001 8:32 PM
> Subject: Re: [VOTE] upgrading to LogEnabled
>
>
> > On Fri, 21
> > > > > I volunteer to do it...
> > > >
> > > > Is the LOgKitManagement able to handle LogEnabled components?
>
> LogKitManager itself is LogEnabled. but It manage org.apache.log.Logger.
> It depend of LogKit.
[snip]
> > > Well, I assumed - since Loggable got deprecated... (I thought _you_
> > >
- Original Message -
From: "giacomo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 21, 2001 8:32 PM
Subject: Re: [VOTE] upgrading to LogEnabled
> On Fri, 21 Dec 2001, Torsten Curdt wrote:
>
> > On Thu, 20 Dec 2001, giacom
On Fri, 21 Dec 2001, Torsten Curdt wrote:
> On Thu, 20 Dec 2001, giacomo wrote:
> > On Thu, 20 Dec 2001, Torsten Curdt wrote:
> >
> > > So should we upgrade cocoon to LogEnabled?
> > >
> > > a) only HEAD
> > > b) HEAD and 2.0
> > >
> > > I volunteer to do it...
> >
> > Is the LOgKitManagement
On Thu, 20 Dec 2001, giacomo wrote:
> On Thu, 20 Dec 2001, Torsten Curdt wrote:
>
> > So should we upgrade cocoon to LogEnabled?
> >
> > a) only HEAD
> > b) HEAD and 2.0
> >
> > I volunteer to do it...
>
> Is the LOgKitManagement able to handle LogEnabled components?
>
> Giacomo
Well, I assum
On Thu, 20 Dec 2001, Torsten Curdt wrote:
> So should we upgrade cocoon to LogEnabled?
>
> a) only HEAD
> b) HEAD and 2.0
>
> I volunteer to do it...
Is the LOgKitManagement able to handle LogEnabled components?
Giacomo
-
Carsten Ziegeler wrote:
> Torsten Curdt wrote:
>
>>So should we upgrade cocoon to LogEnabled?
>>
>>a) only HEAD
>>b) HEAD and 2.0
>>
>>
> I think we should forget the 2.0 branch as soon as possible, so
> changing a) is sufficient.
>
> Before we vote on it, can you identify what really has t
On Thu, 20 Dec 2001 22:35, Torsten Curdt wrote:
> avalon-dev: Can someone please explain why Logger has moved?
> This is giving me some real headaches with the cocoon
> integration - since cocoon still uses Loggable with
> the different Logger.
It wasn't "moved" - it is a new class completely. Th
Torsten Curdt wrote:
> I want to upgrade our cocoon components to use LogEnabled
> instead of Loggable. Most of them extend AbstractLoggable,
> so this is no big deal. But some _implement_ Loggable.
>
> Well, I thought "no big deal either". I changed them to
> implement LogEnabled and renamed th
Torsten Curdt wrote:
>
> On Thu, 20 Dec 2001, Carsten Ziegeler wrote:
>
> > Torsten Curdt wrote:
> > >
> > > So should we upgrade cocoon to LogEnabled?
> > >
> > > a) only HEAD
> > > b) HEAD and 2.0
> > >
> > I think we should forget the 2.0 branch as soon as possible, so
> > changing a) is
On Thu, 20 Dec 2001, Carsten Ziegeler wrote:
> Torsten Curdt wrote:
> >
> > So should we upgrade cocoon to LogEnabled?
> >
> > a) only HEAD
> > b) HEAD and 2.0
> >
> I think we should forget the 2.0 branch as soon as possible, so
> changing a) is sufficient.
That's what I thought, too
> Bef
Torsten Curdt wrote:
>
> So should we upgrade cocoon to LogEnabled?
>
> a) only HEAD
> b) HEAD and 2.0
>
I think we should forget the 2.0 branch as soon as possible, so
changing a) is sufficient.
Before we vote on it, can you identify what really has to be
changed?
>From my memory there
So should we upgrade cocoon to LogEnabled?
a) only HEAD
b) HEAD and 2.0
I volunteer to do it...
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
I want to upgrade our cocoon components to use LogEnabled
instead of Loggable. Most of them extend AbstractLoggable,
so this is no big deal. But some _implement_ Loggable.
Well, I thought "no big deal either". I changed them to
implement LogEnabled and renamed the setLogger() method
to enableLogg
17 matches
Mail list logo