Let me answer that question indirectly. If you use log4j out of the box, expect it to work with the new release. If you extend log4j components, then you can't necessarily expect them to work with the new release.
A small amount of adaptation might be necessary.
Make sense?
At 11:03 PM 12/22/2004, Mark Womack wrote:
What defines the log4j "client API"? o.a.log4j.spi?
-Mark
> -----Original Message----- > From: Ceki G�lc� [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 22, 2004 1:55 PM > To: Log4J Developers List > Subject: Re: setOption/setOptions duality in PatternConverter > > At 10:49 PM 12/22/2004, you wrote: > >I was hesitant to do that if there were external pattern converters that > >would be broken by the change. But if that isn't a concern, then by all > >means. > > No need to worry about external pattern converters. From the log4j FAQ: > > We are very careful not to change the log4j client API so that newer log4j > releases are backward compatible with previous versions. We are a lot less > scrupulous with the internal log4j API. Thus, if your log4j extension is > designed to work with log4j version n, then when log4j release version n+1 > comes out, you may need to adapt your proprietary extensions to the new > release. > > > -- > Ceki G�lc� > > The complete log4j manual: http://qos.ch/log4j/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
