Stefano wrote:
>>>>>> AvalonListserv.java (2 matches)
>>>>> AvalonListservManager.java (2 matches)
>>>> Obsolete and ready to deprecate, IMO.
>>> I love to remove code: can we remove those from trunk?
>>> Wait: deprecate != remove. I'm using AvalonListserv and
>> AvalonListservManager quite extensively, and others may too.
>> This is an example of how caution must be applied to help
>> users upgrade.
> Sure: if we aggree that they should be removed then we should add a
> "deprecate" tag in the current 2.3 release and remove them in our
> trunk for the next release.
Have you noticed how slowly Sun *ever* removes deprecated code? I would remove
such optional pieces (matchers and mailets) only when there is a required
effort to keep the code, and no one wants to make that effort.
And I would move them to a new package, so that the only thing someone had to
do is add the package. That would probably satisfy both you and Vincenzo.
> PS: I don't know why Noel thinks they should be deprecated, I thought
> that a better alternative existed or something similar
Yes, Mark Imel's list manager has long replaced the old one, but that does not
mean that other people aren't still using the old one!
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
