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 wrote:
> OK.. I guess I found the reason.
>
> The directory that gets automatically generated under w
On 12/10/09, Simal 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 rea
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 someon
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 '' needs to be (re)compiled, please run a compile or
use the Compile/Browse
