Mark Diggory wrote:
So, when (which version) would we make this methods available? I'm
concerned that this report suggests that adding methods to an interface
is breaking backward compatibility. When I think the opposite, in that
its breaking "forwards compatibility" of existing application. You tend
to need to break forwards compatibility to make progress on an API's
design.
In out case, adding these methods should only effect a small subset of
the user base (specifically those who may have extended either the
interface or the implementation on their own, effecting them because the
signatures may be incompatible). I'm not even sure if we have anyone in
our userbase actually doing this...
Were I a voting member of [math] I would -1 such an incompatible change
to an interface. Interfaces need to be considered sacrosanct and
unchangable, no matter how painful that is. This is particularly
important in a high profile project like commons, where errors cause
serious implications to users.
We have got this wrong before:
- lang 2.0 deliberately changed the semantics of isEmpty. At least major
OSS user stopped using the library as a result.
- collections 3.0 accidentally changed IteratorUtils.EMPTY_ITERATOR.
Many OSS users still have a bad view of collections as a result.
Although the causes were different, the effect was the same. Thats why
we should be running a tool like clirr for each commons release. As,
I've said before, commons needs to strive to be whiter than white.
Lets not to get it wrong again when we have found the issue.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]