On 10/30/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 10/30/06, Torsten Curdt <[EMAIL PROTECTED]> wrote: > > There are clearly good reasons / circumstances to take the approach > > you suggest, but it is a user unfriendly approach. As a user I like to > > try out new versions by dropping in a new jar - before taking the > > decision to upgrade. This approach rules that out and it wouldn't > > surprise me if users started to see commons as irrelevant because of > > "upgrade hell" if we take this route too often.
...
I didn't argue in this thread against changing package names - just against mandating it as a policy.
Even re-reading the above paragraph that is not what I am reading in it ...but anyway.
I agree that if, as in the example of Generified Collections, the developers choose to refactor then changing the package name is a necessary approach. However the Collections developers have/had a choice - they could have adopted the approach Sun took to generics and preserved backwards compatibility.
I think that's not even what this proposal is about. It's about the case when it is either not possible ...or decided not to keep this compatibility. So if there is no way of "dropping in" the jar there should be a change of the major version number ....AND so this should also require a package name change. It think this is about contracts ...and all components should adhere to that. What we do with Collections should be discussed outside this thread ...IMO
Both options are valid - but it should be down to individual components to choose the route they take. If Collections had chosen this route then mandating a package name change would be stupid.
P.S. Your analogy is irrelevant as it doesn't represent any POV I put forward.
Without putting oil into a fire I'd like to carefully note that "Irrelevant" and "stupid" are words you should be careful with in discussions. cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
