On 1/10/07, Joerg Heinicke <[EMAIL PROTECTED]> wrote:
Rahul Akolkar <rahul.akolkar <at> gmail.com> writes:
> > "Generally speaking, an interface-compatible change will at most change the
> > private interface of a component, or simply add classes, methods and
> > attributes whose use is optional to both internal and external interface
> > clients."
>
> And this is not.
In which way is it different from "simply add [..] methods [..] whose use is
optional to both internal and external interface clients." ??
Even simply replacing the former jar with the next version should work as the
client does not know about the new methods. Only recompilation of
implementations need adaptions before but that's not what I consider a "use" or
a "client".
<snip/>
I suspect that bit is talking about Java classes (rather than
interfaces), though I haven't tried to hunt it down in the guide. I
flagged what I thought would lead to a versioning discussion at 1.2
voting time. Lets please move on, the Commons versioning criteria are
quite objective, and I have nothing to add.
-Rahul
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
