To all GWT contributors-

As you may know, there many exciting
things<http://code.google.com/webtoolkit/makinggwtbetter.html#roadmap>
we're working on for GWT 2.0. With all the new features coming
your way we thought GWT 2.0 would be a good opportunity to clean house
and remove previously deprecated methods and classes. In
many cases an equivalent replacement is suggested in the Javadoc and
updating your projects should hopefully not be too onerous.

While different sections of the API have been deprecated in different
releases we wanted to make things as straightforward as possible for the
upcoming release. As such, our plan for GWT 2.0 is to remove everything that
was marked as deprecated in previous releases. We did not introduce any new
deprecations in GWT 1.7 so you can find the complete list of items we plan
to remove in this GWT 1.6 document:


http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/deprecated-list.html


If you have any serious concerns about the above deprecation list, please
reply back to indicate how you will be affected. In particular I'm
interested in any use cases in the GWT 1.6/1.7 API which you feel would not
be covered in GWT 2.0 once the @deprecated methods and classes have been
removed.

Please note that Java compilers are required to warn
you<http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/deprecation/deprecation.html#how>
when
your code uses @deprecated methods or classes. Although there are warning
suppression mechanisms such as the @SuppressWarnings annotation and your
IDE's or build environment's settings. So, in general, chances are you are
probably not using any deprecated GWT APIs without knowing about it.

Thanks--
Fred Sauer
 Developer Advocate
Google Inc. 1600 Amphitheatre Parkway
Mountain View, CA 94043
[email protected]

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to