I finally got it to work. I commented out <add-linker name="xsiframe"/>
in my XXXX.gwt.xml and deployed it. It really started acting weird - complaining about X-Frame-Options set to deny....Then I re-added the linker code and deployed and things started finally working. On Sunday, September 6, 2015 at 6:38:23 PM UTC-7, [email protected] wrote: > > I rolled back to 2.6.1 to see if the issue would go away - but is still > persist. I've done mvn clean, full rebuild and deploy and I am still > getting the annoying dev mode popup. Any other suggestions? Are there > settings I am missing to do a "production" compile? > > On Sunday, September 6, 2015 at 2:54:12 PM UTC-7, Jens wrote: >> >> You should always do a mvn clean before doing a production compile so you >> can be sure you start from a clean state without anything SDM might has >> produced. >> >> Also GWT 2.7 (and 2.8-SNAPSHOT) has a timestamp bug for the >> <module>.nocache.js file which is probably the cause of your issue: >> >> https://github.com/gwtproject/gwt/issues/9108 >> >> https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/q4BgTzs6PXw >> >> -- J. >> > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
