Hi Pascal, Am 03.03.2017 um 23:33 schrieb Pascal Schumacher: > Hi Oliver, > > guess clirr is complaining because changing the parameter type of > methods is not binary compatible: > > http://stackoverflow.com/questions/1365409/refactored-methods-and-binary-compatibility-in-java > > > http://wiki.eclipse.org/Evolving_Java-based_APIs_2
yep, it was late yesterday. I came to the same conclusion after switching off my computer. The change is source compatible, but not binary compatible. I guess our best bet is to add new overloaded methods using the new parameter type and let the old ones delegate. Thanks Oliver > > -Pascal > > Am 03.03.2017 um 22:32 schrieb Oliver Heger: >> Hi, >> >> in CONFIGURATION-653 [1] it is proposed to change the type of some >> method parameters of utility methods from Configuration to the base type >> ImmutableConfiguration. This makes those methods broader in scope. >> >> I would expect that this is a change which should not affect client >> code. Nevertheless, clirr reports errors in these cases. I could imagine >> that there was a risk to break clients that override one of these >> methods. But they are static, so this should not be an issue. >> >> Do I miss something? >> Oliver >> >> [1] https://issues.apache.org/jira/browse/CONFIGURATION-653 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
