Am 02/04/17 um 11:33 schrieb Stephen Connolly: > Yep I don't think it is a good idea to make them final > > We could add some tooling to the Maven-plugin-plugin to scan for annotated > method (would need a new annotation) so that plugins using or overriding > would get a hard error (similar to @Restricted(NoExternalUse) in Jenkins > > That would allow to retain binary compatibility for existing compiler usage > but force code fixes when building new plugin releases
My point is that if someone has overridden the old method, that method may no longer get called as soon as everything gets updated to no longer call the deprecated methods but the new ones. So if we do this, we should not update anything to call the new methods and should instead keep everything calling the old/deprecated methods due to this. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
