On 16 nov, 17:41, Chris <crehb...@gmail.com> wrote: > Hi, > > I'm working on upgrading our development environment from GWT 2.0.4 to > 2.1 - this involved upgrading GPE to 1.4 as well as the gwt-maven- > plugin to 2.1. So far things have gone pretty smoothly except for one > nagging problem. > > We have in our code tree a POM module that holds just shared resources > - images & CSS - that we make available to all GWT modules in our > codebase. This is managed by maven-assembly-plugin that unpacks a zip > file from the repo into our target/<GWT module> directory. > > 'mvn package' builds the directory structure correctly, and the > resultant war file can be deployed to an external Tomcat server with > no problem. But when I try to run the app in developer mode it seems > that GPE is deleting the maven-assemly-plugin managed resources prior > to startup. > > I've tried just about everything I can think of, but can't for the > life of me figure out why this resources directory is being removed. > Has anyone ever had a problem like this?
Well, if your resources are to be shared with GWT apps only, then how about making a GWT module and putting them in the "public" path, so the GWT compiler copies them to the output folder? Or maybe those resources shouldn't be put into that folder to begin with (it has always been the case that the <module-name> folder is "GWT controlled" and always cleared by the GWT compiler before it actually generates anything; it might have not always been the case for DevMode but I don't see an issue with DevMode doing the same thing as the compiler). As a last resort, you can still use -noserver... -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
