deprecate methods using Category and
> replace them with
> >> > versions using Logger. At some point Category will be
> going away, so we
> >> > should prepare folks now.
> >> >
> >> > Regarding the indentation, I am using JCreator for my
> edito
I'll try it again tonight.
thanks,
-Mark
> -Original Message-
> From: Ceki Gülcü [mailto:ceki@;qos.ch]
> Sent: Thursday, November 14, 2002 12:51 AM
> To: Log4J Developers List
> Subject: RE: Problems adding new listener interfaces
>
>
>
> My bad. I
it] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.
main(JUnitTestRunner.java:409)
[junit]
BUILD FAILED
> -Original Message-
> From: Mark Womack [mailto:mwomack@;bevocal.com]
> Sent: Wednesday, November 13, 2002 9:48 AM
> To: 'Log4J Developers List'
> Subject: RE: Problems adding new listen
com]
> Sent: Wednesday, November 13, 2002 9:48 AM
> To: 'Log4J Developers List'
> Subject: RE: Problems adding new listener interfaces
>
>
> OK. So, I will deprecate the fireAddAppenderEvent(category, appender) and
> create a new version fireAddAppenderEvent
.
>
> I'll be checking more stuff in tonight.
>
> thanks!
> -Mark
>
> > -Original Message-----
> > From: Ceki Gülcü [mailto:ceki@;qos.ch]
> > Sent: Wednesday, November 13, 2002 4:09 AM
> > To: Log4J Developers List
> > Subject: Re: Prob
nesday, November 13, 2002 4:09 AM
> To: Log4J Developers List
> Subject: Re: Problems adding new listener interfaces
>
>
>
> AFAIK, the only place where HierarchyEventListener interface is
> actually used to get work done is in the o.a.l.jmx package. Our
> current JMX supp
AFAIK, the only place where HierarchyEventListener interface is
actually used to get work done is in the o.a.l.jmx package. Our
current JMX support is half-baked. So, I would not have any qualms to
just remove HierarchyEventListener and by implication change the
LoggerRepository interface and the
