Improve standalone deployment documentation

[ceedubs]

There are a number of things we could document better in the Standalone Deployment page.

• merge strategies to avoid conflicts with about.html etc
• set the 'mainClass in assembly' config to JettyLauncher
• change the Jetty dependencies to "compile;container" from just "container"

This is mostly a reminder to myself to make this contribution, but I don't think the way I'm doing the first item on the list is the most sane way to do it, so if someone else wants to chime in with the best way to accomplish that, feel free :)

[futurechimp]

Hi ceedubs, does this one relate to #50 at all? I saw this discussion fly past on the list and in IRC, but I'm not exactly Captain Servlet so can't help out too much.

[ceedubs]

Hmm, I never followed up on that whole statement about this issue being a reminder to myself to make this contribution, did I?

This is definitely related to #50. However, I'm also saying that we need to talk about the things that need to happen outside of the bootstrap class to create a standalone server, such as changes to build files, etc.

I am not sure I ever went about this in sane way in the first place, and it's been a couple months since I worked with this, so I would have to try to figure it out again. I can take a shot at it this weekend, but if there is someone else who knows this stuff well, it would be great if they could document it a bit.