On 10/25/06, James Carman <[EMAIL PROTECTED]> wrote:
For someone who uses Commons Collections a lot in their applications, this is going to be quite a pain if I want to upgrade. Yes, I realize that there's such a thing as find and replace, but the fact that I have to do that if I want to upgrade is just a bother. That's my $0.02.
Well, easy ...then you don't upgrade ;) Sorry, but the fact that an upgrade is not always is as easy as replacing a jar is not an argument (IMO) As long as there is an upgrade path it's up to the user to walk that path or not. The important thing though is to have such a path. cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
