Thanks for the helpful information. I was able to get jetty & tomcat to serve
static resources by placing them in a static folder at the root of my web app.
The only wrinkle was that WO was generating links to my application bundle
resources without the “Contents” part of the URL as in your scre
I wouldn't bother with a split install. Just serve the web server
resources directly from tomcat/jetty. That's one of the main advantages of
using a war in the first place - a much simpler deployment that just
works. Everything third question on this list is from someone having a
problem deployi
How are maven folks doing split installs when packaging as a true war
for tomcat (or whatever container)? I've recently converted my app to a
true war, but the webserver resources are now bundled in the war and
there is no webserver-resources archive generated anymore (at least not
that I can find)
