Yes, there are a few other types of resources that may be necessary
too (other stuff the shell needs, for server side resources, etc).
I will look into this more though, I thought the regular filtering via
the webapp plugin still worked for WARs (who cares what's in the
shell, as long as it works, but deployment artifacts do need to be
clean).
What setup did you try to filter the resources?
I believe if you do something like this to configure the WAR plugin,
it works fine?
<webResources>
<resource>
<directory>target/gwt</directory>
<excludes>
<!-- Filter out unwanted build artifacts -->
<exclude>**/whatever/**</exclude>
</excludes>
</resource>
</webResources>
Maybe it would be sufficient to add that to the FAQ? Try that please,
if you haven't, and let me know if it accomplishes what you are trying
to do.
On Oct 2, 9:17 am, MiSt <[EMAIL PROTECTED]> wrote:
> > And this solved my problems. Are there any reasons why this lines are
> > necessarry ?
>
> Ok, I can answer my own question ;).
>
> Thanks to resources dir at classpath you can edit css files and see
> changes without gwt browser restart.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
