On 31 mar, 16:01, "Robert \"kebernet\" Cooper" <[email protected]> wrote: > The point of filtering is that it is going to write resources to > target/classes. By default, the gwt-maven:gwt goal puts your sources and > resources folders on the classpath when it starts GWT shell. This lets you > do things like, say, edit a CSS file and hit reload in the shell and see the > change. Toggling resourcesOnClasspath removes this, so the only resources on > the boot path for GWTShell become the ones that are filtered in your > target/* structure. > If you are using filtered resources, you will need to do something like > "maven war:webapp gwt:gwt" on the older versions. In the current SVN for > RC1, the gwt-maven:gwt goal has been moved to the install phases, so it > should preprocess all your resources into their proper place when you start > it. You will then need to do, war:webapp again to change the resources that > are getting packages.
That would probably be mvn war:exploded I had confirmation that it was related to the goal moved to installed, the rest is probably OT here, but to answer Brian, here what I do : source/resources with refs to properties --filtering--> sources/ resources --deferred binding--> running code. The deferred binding part is not unlike the i18n part of GWT, and the matching property files are filled using maven filtering. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
