replace your 1.5.3 libs with the 1.6 libs ... that's pretty much it ... if the compiler wants to put your code in war/ then add the compiler flag -war www to get it back to the 1.5 way of doing things ...
from there, you should be good to go. you can migrate from listeners to handlers as time allows, they are deprecated, but not removed so no need to do any work if you don't want to :-) this really isn't that tough of an upgrade. -jason On Apr 9, 2009, at 11:48 AM, Ed wrote: > > Hi all, > > I am running in no-server mode with GWT 1.5.3 > > I read bits and peaces about the changes, but still not completely > sure how to merge to GWT 1.6. > > How/Where can I find the changes that will effect my no-server > configuration? and what about my gwt directly structure ? I like it as > it is and don't want it in a war :(... as I perform a separate > deployement for the java backend and my gwt front -end. > BTW: I am using my own Eclipse launch files to start in hosted mode... > I think that also changes... > > Maybe it will be very easy to merge to GWT 1.6, but any tips will be > more then welcome to overcome afterwards thoughts like "If I knew > that... ".... > > -- Ed > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
