You are talking about Java interfaces, not interfaces in general or different interface definition languages (like WSDL)?
For Java interfaces: No. That's why changing an interface is expensive. Some use even version numbers in interface names (Eclipse project, IIRC; or java.awt.LayoutManager which got a new version with java.awt.LayoutManager2).
In the latter case you eventually can generate the Java classes automatically from the IDL. Then it is a little bit easier.
(A)Suppose your question is about Java Interface:
1) you have many subclasses that implement the Java Interface provided in jar file
2) you are using coding to interface (e.g. InterfaceABC abc = new ClassMyImpl(); )
3) so polymorphism happening around all your client code
Suppose some x only change the Java Interface name , and method name left unchanged
Old Java Interface name: InterfaceABC
so your implementation classes name: ClassMyImpl implements InterfaceABC
now some x change the Interface name to: InterfaceXYZ
you create a new Interface with name: InterfaceABC extends InterfaceXYZ
you don't need to change your implementation classes name and all the client code that using polymorphism.
(BUT this will break polymorphism which calling method of implementation classes in jar file, because different class hierarchy)
(B)Suppose your question is about interface (means method definition) instead of the Java Interface:
Solution: use Design Pattern "Adapter Pattern"
SCJP 6, SCWCD 5, SCBCD 5
A feeble attempt to tell you about our stuff that makes us money