Thomas, what do you mean by "touch" your no cache.js file? I have
this Chrome caching issue not only when rolling back, but also when
deploying new version. Is there a way to do this via ant or during
the GWT compile? My ant compile looks like this.
<target name="GWTCompiler" depends="compile" description="Run GWT
compiler">
<java fork="true" classname="com.google.gwt.dev.Compiler"
failonerror="true">
<jvmarg line="-Xmx512m"/>
<classpath>
<pathelement location="${lib}/gwt-user.jar"/>
<pathelement location="${lib}/gxt-2.2.5-gwt22.jar"/>
<pathelement location="${external_lib}/gwt-2.4.0/gwt-
dev.jar"/>
<path location="${src}"/>
<path location="${gwt_home}"><fileset dir="$
{gwt_home}" includes="*.jar"/></path>
</classpath>
<arg value="-logLevel"/>
<arg value="WARN"/>
<arg value="-localWorkers"/>
<arg value="4"/>
<arg value="-war"/>
<arg value="${gwt_compile_outputdir}"/>
<arg value="-style"/>
<arg value="Detailed"/>
<arg
value="com.artisan.clientReporting.ClientReportingMatrix"/>
</java>
</target>
On Feb 6, 2:41 pm, Thomas Broyer <[email protected]> wrote:
> Your browser asks for the no cache.is with an If-Modified-Since header, so
> once you get a fresher file you cannot get back an older one. You should
> "touch" your no cache.js file so it has a later modification date.
--
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.
