Hi Bill,

I've had success with just doing a regular build to update GWT apps when running in development mode. It's worth verifying that you are running with -Ddevmode=true in your Tomcat debug VM parameters, as it affects how the server set caching headers for .js files.

Assuming you're running in dev mode and are still seeing the problems, what module does the GWT app belong to? After edit your GWT app and a regular build (not a rebuild) does the corresponding .module file in <LABKEY_ROOT>/build/labkeyWebapp/modules get updated with a new timestamp? What about the files in <LABKEY_ROOT>/build/labkeyWebapp/explodedWar/<YOUR_GWT_PACKAGE>?

Thanks,
Josh

Hi Josh,
Just knowing that it normally works the way I was doing it is a big help. It tuned out to be IE casching the page. I guess it only looks for the source of the page to change but not changes in the java script that it points to. Firefox doesn't have this problem.

Thanks,
Bill