This issue is that [collections] is in wide use. Stephens proposal allows all existing applications to use the future releases (of [commons]) without code change, only requiring that commons-lang.jar be added as a dependency. This is especially important if your application depends on third party software (that you don't have source code access to) that also depends on [commons].
-----Original Message----- From: Emmanuel Bourg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 8:11 AM To: Jakarta Commons Developers List Subject: Re: [VOTE][collections] Functors, dependency from collections to lang Rodney Waldhoff wrote: > On Fri, 13 Dec 2002, Stephen Colebourne wrote: > I think this proposal would be more accurately considered a product change > (it removes public classes from a released component and adds a new > dependency to a released component, arguably it changes the scope of two > released components) and hence would require [lazy] consensus approval. > I.e., this is a veto-able action. I may be missing something but Stephen's proposal is to deprecate and not remove public classes from collections. I don't see the issue in adding a dependency on the next release of collections. Emmanuel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
