GWT2.8.0-beta1 and net.ltgt.gwt.maven plugin issues in super dev mode

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.

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>

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.

--
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.