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.