To avoid this problem, you can write abstract classes that implement
the interfaces. If third party implementations then extend the
abstract class there's no backward compatibility issue.
Of course, if you add functionality to the interface that needs to
have a specific implementation (not
I'd suggest taking a look at guidelines that other Java projects have
established to get an idea of consequences.
Here is the one for Eclipse:
http://wiki.eclipse.org/Evolving_Java-based_APIs
There are probably some Apache projects that publish something similar.
Mark
On Fri, Mar 26, 2010 at
Mark,
A couple of months ago, you mentioned the avenue of interface-izing the various
objects that are part of the public API, such as the callbacks and the client
interface. In thinking a bit more about this, and given my general lack of
Java background (in spite of the recent commits to the c
3 matches
Mail list logo
