GWTShell Caching?

[siberian]

Hi,
Late last week my dev partition ran out of disk space and eclipse got flaky (rightfully so).

Every since fixing the disk space issue GWTShell seems to be caching my application. My package is com.pgi.gwt and for not fully understood reasons this app has started telling me I am missing the chrome plug-in and trying to load in hosted mode.

In my debugging efforts I downloaded the latest version of Eclipse, created a new workspace and installed the latest version of GWT Designer.

What I find is that if I create a project in this brand new eclipse/gwt designer with a module that uses the com.pgi.gwt namespace I get the same error as I did in my original eclipse install. If I use a new package name (com.company for example) everything works fine, the only difference between the two being the namespace itself.

Any tips? I am dead in the water 2 days on this and the references I find on the google groups point back here (even though it feels like a generalized issue, not Instantiations specific).

Tx
John-

[Eric Clayberg]

Every since fixing the disk space issue GWTShell seems to be caching my application. My package is com.pgi.gwt and for not fully understood reasons this app has started telling me I am missing the chrome plug-in and trying to load in hosted mode.

We have never heard or seen anything like that.

What I find is that if I create a project in this brand new eclipse/gwt designer with a module that uses the com.pgi.gwt namespace I get the same error as I did in my original eclipse install. If I use a new package name (com.company for example) everything works fine, the only difference between the two being the namespace itself.

That sounds truly bizarre.

I am dead in the water 2 days on this and the references I find on the google groups point back here (even though it feels like a generalized issue, not Instantiations specific).

It definitely doesn't sound like anything related to GWT Designer. What references in the Google groups point back here?

[siberian]

Seems related to 2.0. Last night I fixed it based on the below thread:

http://groups.google.com/group/google-w ... 156ea83cbd

The only way I got it to fix was to create a new GWT Project with a new entry point and package name and then copy my OLD entry point code into the new entry point file. Then I could copy over the rest of my source, hand edit my web.xml and then i was back in business.

This all occurred on my mac when I tried to use GWT 2.0. Seems others have the same problem.

Anyhow, not an instantiations issue, something is up with GWT. When even a new eclipse + new workspace + new plugins don't fix it you know your in MagicLand..

John-

[Eric Clayberg]

Thanks for the info.