minor sdm bug

[Stephen Haberman]

Hey,

I was trying SDM on a project today, via the -superDevMode flag that
was added to DevMode (great work).

It worked really well on one project, and then on another I kept
getting the "GWT needs (re)compiled" that's from the old
<module>.nocache.js.

Turns out I had a <module>.nocache.js.gz artifact that was from some
previous compile I had done (with Precompress included), and Jetty was
serving this old .js.gz as the preferred version of the nocache.js file.

So, I'm not super familiar with where/when the files get generated, but
maybe SDM could detect/delete/update the potentially-stale .js.gz
version of the nocache.js file?

Thanks,
Stephen

[Brandon Donnelson]

If you get the re-compiled issue, delete the target or compiled folder, I suspect the nocache.js is cached and has to be deleted by hand. This will happen when switching back in forth between devmode and super dev mode. 

[Brandon Donnelson]

I'll change my comment some. :) 

I know its the nocache.js is getting cached after much testing with GPE switching back in forth. So the question is should the compiler update nocache.js each time?

[Manuel Carrasco Moñino]

On Mon, Sep 29, 2014 at 6:37 PM, Brandon Donnelson <branfl...@gmail.com> wrote:

I'll change my comment some. :) 

I know its the nocache.js is getting cached after much testing with GPE switching back in forth. So the question is should the compiler update nocache.js each time?

The problem here is not updating the .nocache.js which is being updated, but remove the nocache.js.gz if the folder was not cleaned previously. I think this could be added to SuperDevModeListener.

 

On Monday, September 29, 2014 9:35:35 AM UTC-7, Brandon Donnelson wrote:

If you get the re-compiled issue, delete the target or compiled folder, I suspect the nocache.js is cached and has to be deleted by hand. This will happen when switching back in forth between devmode and super dev mode. 

On Sunday, September 28, 2014 4:21:45 PM UTC-7, Stephen Haberman wrote:

Hey,

I was trying SDM on a project today, via the -superDevMode flag that
was added to DevMode (great work).

It worked really well on one project, and then on another I kept
getting the "GWT needs (re)compiled" that's from the old
<module>.nocache.js.

Turns out I had a <module>.nocache.js.gz artifact that was from some
previous compile I had done (with Precompress included), and Jetty was
serving this old .js.gz as the preferred version of the nocache.js file.

So, I'm not super familiar with where/when the files get generated, but
maybe SDM could detect/delete/update the potentially-stale .js.gz
version of the nocache.js file?

Thanks,
Stephen

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/e8a1cc47-2870-485c-a948-82c8df3f494b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.