So should I conclude that the problem I am seeing is caused by bugs in Super Dev Mode ? It seems that the files written in the %TEMP% folder are not always correct and it breaks SDM. It seems that it starts happening when I make a code change that does not compile and I refresh the browser. Sometimes it can recover but sometimes it doesn't and it start behaving erratically. The only solution at that point is to clean the temp folder and restart SDM.
On Thu, Feb 11, 2016 at 3:40 PM Thomas Broyer <t.broyer@gmail.com> wrote:
On Thursday, February 11, 2016 at 2:57:34 PM UTC+1, DavidN wrote:I'm using Thomas excellent maven integration with GWT 2.8.0-beta1 in combination with super dev mode and tomcat. As generated by the maven artifacs.I sometimes have really strange issues where it seems that the super dev mode updates do not seem to be correct.Suddenly I get ClassCastExceptions on types that should never be anything else, things that did not change at all.Cleaning the mvn project and rebuilding does not work.When I clean the %TEMP% folder of all gwt related artifacts then SDM works fine again.This is really annoying since it is not always clear if I just added a new bug in my iteration or the SDM is serving something corrupted.I was looking into avoiding this problem, by making sure that the GWT compile and SDM do not rely on the %TEMP% folder but use a folder inside the project target folder.This is already the case by default (contrary to Mojo's plugin):For that there are 2 different configuration parameters (work and extra):I've set them to this in the pom.xml, yet I still see files being generated in the %TEMP% folder.<workDir>${project.build.directory}/gwt/work</workDir>
<extra>${project.build.directory}/gwt/extra</extra>
Note that if "extra" is not set, GWT shouldn't write the "extra" files to disk.This is only applicable to gwt:compile though (gwt:codeserver and gwt:devmode will write extras into subfolders of their respective codeserverWorkDir and devmodeWorkDir; CodeServer writes into subfolders of its -workDir, and DevMode simply calls CodeServer)Did these parameters change in GWT 2.8.0-beta1 or are there other folders I need to reconfigure or is there an issue in the maven plugin ?I see CssResources, Gin related files and gwt- files being generated in the %TEMP% folder regardless of my settings.--I don't think anything actually changed in GWT, it always outputted some files to the temp folder.As a workaround, you can set the java.io.tmpdir system property (theoretically):<systemProperties><java.io.tmpdir>${project.build.directory}/gwt/tmp</java.io.tmpdir></systemProperties>
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment