I can't remember when the structure changed, but did 1.6 have the WAR compile setting? Instead of it compiling to the WWW folder? If it didn't have the WAR it may be easier to create a new GWT project and import all your .java files and place all the pics and such in the WAR.
Have you tried creating a brand new 2.0 project making sure you can run and compile that, just to verify all plugins are installed correctly? If you can create a new project, but still have problems importing the old one, I'd create a fresh Workspace, create a Fresh GWT project with the same name as your old one and then just import your .java's and put all the other files you need (.css, .xml .png's) and such in the correct spots as well. On Feb 1, 11:39 am, jonbbbb <[email protected]> wrote: > Hi, > > I have upgraded to Gwt 2.0 from 1.6. > > Previously in 1.6 I could compile the project into javascript by > hitting the compile button in the window that came up when I ran the > project. > > If I now in Gwt 2.0 hit the red suitcase button in eclipse, I get a > "Gwt compile" dialog up. But it has an red x, and says "...is not a > Gwt project". And the compile button is disabled so it is not possible > to compile it. > > Any ideas why it thinks it is not a Gwt project? And how can I compile > it? > > Regards, Jon Berg. -- 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.
