(Moving conversation to contrib). The question is can we remove a very public interface from our API without deprecating it first, even if we java doc that it is going away?
For instance, a user might be storing a set of clickable gwt widgets in a List<SourcesClickEvents>. That code would not produce any deprecation warnings, yet would break when we removed SourcesClickEvents from the API. Would that be acceptable to our users? On Thu, Dec 11, 2008 at 6:56 PM, <codesite-nore...@google.com> wrote: > > Comment #3 on issue 3194 by ray.ryan: Need to deprecate SourcesXXXEvents > interfaces so we can remove them later > http://code.google.com/p/google-web-toolkit/issues/detail?id=3194 > > I don't follow this reasoning. Why can't we remove them? > > Why not just tweak their javadoc to say something like "you'll note that > every method in this interface is > deprecated. We have refrained from deprecating the interface itself to keep > from flooding the code base with > unsurgical @Suppress() annotations, but none the less it will be removed > from the next major GWT release." > > Clients will have had to stop implementing the interfaces in order to > remove the method deprecation warnings. I > just don't see the issue. > > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences at: > http://code.google.com/hosting/settings > -- "There are only 10 types of people in the world: Those who understand binary, and those who don't" --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
