I was thinking that too. Seems like a good compromise between compatibility and cleanup.
On 10/23/07, Jörg Schaible <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] wrote on : > > > That's certainly the solution of least impact and works for me. Sucks > > that we would have to keep a whole dependency for one deprecated > > method in one deprecated class, but life is hard sometimes. > > We may set it to optional though and point it out inthe release notes. > > - Jörg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
