On Thursday, November 22, 2012 9:13:25 PM UTC+1, Paul Robinson wrote: > > > On 22/11/12 17:16, Jens wrote: > > > > If its only renaming a package from X to Y then, as a developer, I am > totally fine if my code becomes broken after updating GWT because I could > fix that via some IDE automatism like organize imports or a global > search/replace on import statements. As long as its well documented in the > release notes, so it does not hit me like a surprise, this should be fine. > +1 >
The only problem with this is that, without a (deprecated) indirection, you'd be forced to wait that all your 3rd-party dependencies (that depend on the renamed classes) update to the new version of GWT before you can update too. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
