Hi,

> -----Original Message-----
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: 13 May 2005 04:49
> To: Log4J Developers List
> Subject: Re: [VOTE] Release Overview
> 
> 
> On May 12, 2005, at 6:44 PM, Andy McBride wrote:
> 
> > Hi,
> > The current cvs head contains breaking changes including the
> > removal of
> > org.apache.log4j.jmx.HierarchyDynamicMBean,
> > org.apache.log4j.spi.ErrorHandler and
> > org.apache.log4j.spi.ErrorCode without
> > any apparent replacement or deprecation cycle.
> >
> 
> Nice to know some names of the disappeared.  Is that a complete list?

No just the ones that broke the app I tried the upgrade on. 

> 
> 
> > The removal and re-implementation of
> > org.apache.log4j.RollingFileAppender
> > does not maintain compatibility with existing code as it claims in the
> > javadoc as it does not support subclasses.  Again no deprecation
> > cycle.
> 
> Probably need to clarify the JavaDoc, though the explicit "final" on
> the class indicates that it wasn't intended or expected to be
> compatible for extension, though hopefully it is compatible for use.
> The primary motivator was to allow projects that had used, but not
> extended, o.a.l.RFA and o.a.l.DailyRFA to work with both 1.2.x and 1.3.
> 

The class was not final in 1.2.9 therefore the API was open to extension.  

I'm quite happy to refactor my code to utilise a better rolling API but a
deprecation cycle would have been nice to give advance warnings about
potentially incompatible code.  

I thought the whole point of 1.2.9 was to enable users to 'prepare' for
incompatible API changes in 1.3?  The app I tried was working happily with
1.2.9 so I was unprepared for the changes required to upgrade to 1.3alpha.  

Either a whole lot more documentation needs to be written or a new release
produced which marks the relevant classes and methods as deprecated.  

Regards

Andy



> 
> ---------------------------------------------------------------------
> 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]

Reply via email to