What should commons do when projects get released with unplanned binary incompatabilities that cause issues, as with collections IteratorUtils?
I can see two basic solutions: 1) Procede onwards, and tell users to upgrade to the later version. This may not be possible if two OSS projects have built against two versions of the library. 2) Produce a replacement build that puts the API back to how things were. This causes problems for anyone who built against the newer version of the library. For example, should [collections] next release be 4.0 instead of 3.1, such that 4 is compatible with 2.1 but not 3? Release 3 then becomes deprecated. Or does this just create another round of problems. Any other bright ideas??? Stephen PS. The particular problem is in IteratorUtils where 6 methods and 2 constants changed return type, which is binary incompatible. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
