On Thursday, February 14, 2013 2:11:21 PM UTC+1, Paul Robinson wrote: > > While it's good to get rid of long-deprecated things, is it really a good > idea to do that in a point release like this? Shouldn't it wait until GWT > 2.6? I'm thinking in particular of GWTShell and GWTCompiler.
GWTShell and GWTCompiler have been deprecated since GWT 1.6, first released 3 years ago (1.6.0 is dated Feb 4th) HostedMode was the replacement for GWTShell in GWT 1.6 and has disappeared long ago, replaced by DevMode (there's still a HostedMode entry point, but it simply says "hey, I'm deprecated, use DevMode instead" and exits: that was in Sept/Oct 2009 !) GWTShell survived HostedMode only because JUnitShell was still based on it for a while (until April 2010, when it was rewritten to extend DevMode instead, and thus use Jetty instead of Tomcat). Removing GWTShell was a long-overdue task, we're just removing clutter here. This allows us to remove the Tomcat dependency and stop bundling it into gwt-dev.jar (which almost balances the growth of ICU, so that gwt-dev * only* grows by 1MB instead of ~3MB) So if you ask me, yes, it's a good idea doing this even in a point release. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
