I had similar problems upgrading. Did all the right things, new libs, DevMode, cleaned, rebuilt.
Finally, I found I had to clear FF's cache as well -- very frustrating. On Dec 10, 4:40 pm, Simal <simalhance...@gmail.com> wrote: > OK.. I guess I found the reason. > > The directory that gets automatically generated under war, the one > that has the module name, had to be deleted. I think the contents of > that folder were not getting updated after I compiled with GWT 2.0 and > it was kind of reading from cache. > > Hope this helps someone.. > > - Simal > > On Dec 10, 12:21 am, Simal <simalhance...@gmail.com> wrote: > > > Hi all, > > > I'm sure this is related to build/run configurations but couldn't > > figure it out after a long day.. > > > I'm upgrading from GWT 1.7 to 2.0 and when I try to open up my > > application in a browser, I get the > > "GWT module 'xxxx' needs to be (re)compiled, please run a compile or > > use the Compile/Browse button in hosted mode" message. > > I think this message is somehow from GWT 1.7 (since we no longer have > > a Compile/Browse button in the hosted mode in 2.0). > > I'm using Eclipse. I changed my build path and run configurations to > > use the GWT 2.0 jar files. My war/WEB-INF/lib directory contains the > > GWT 2.0 gwt-servlet.jar as well. I don't quite understand why it's > > referring to a message from an earlier GWT version. > > > Can anyone think of a point I might be missing? Any other > > configuration I should be looking into? Any specific ordering of the > > jar files in the build path or run configurations? Any caching that > > might be happening? > > > Thanks in advance, > > Simal -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
