Am Donnerstag, den 13.07.2006, 20:31 -0400 schrieb Noel J. Bergman:
> > Btw my personal opinion is that James needs new features
>
> > - IMAP
>
> Agreed. And we have a lot of protocol support for it. I have an idea for
> resolving the store issue.
I'm very curious to hear about it! I tried t
Noel J. Bergman wrote:
Stefano Bagnara wrote:
About this deprecation issue [you] would like to deprecate some code
and I reply with +++1. If you don't want to deprecate it, well, I'm
ok anyway.
Oh, I want to mark it as deprecated, and see what feedback we get.
My way of think
Stefano Bagnara wrote:
> That said you once said that we could deprecate things in a version and
> change them in the following one.
I seem to recall saying that is what a particular large vendor does, and I
wouldn't have much of an issue with it. But if a user raises a concern, I'd
support i
Noel J. Bergman wrote:
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 (matche
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 exten
