Hi, > > In fact, changing the return type does break binary compatibility (binary > compatibility is different from source compatibility), since the return > type of a method is part of is java signature. > This means that if someone would want to use the new jar (with changed > return type) as a drop-in replacement, without recompiling anything else, > the code would not execute (without NoSuchMethodError thrown). > Thanks for these explanations. I guess this change will have to wait !
Sébastien --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
