initial support for logback based request logging
add jmx jetty config such that it can be specified as an app parameter
remove faster windows example

The only difference was one property value, so documented this at

https://support.sonatype.com/entries/30167973

in the rare case this is needed.
remove header buffer size example

not only has the default header buffer size changed from stated 4 k to 6 k in Jetty 8, I don't even think the hack this was working around even applies anymore. According to https://docs.sonatype.com/display/SPRTNXOSS/Jetty+Configuration#JettyConfiguration-IncreasingJetty'sheaderbuffertocopewithUIcolumnresizing a http request header was used to send column sizes to the backend? I did a bunch of table column resizing and didn't notice a thing.

Further in the past 10 months, I never heard this come up once from a customer.
with new jetty-requestlog.xml, we don't need this example anymore
remove jetty.xml copy of ../jetty.xml

any administrator can either restore the original from the original bundle, or make a copy before they start editing the real one
JMX doc tweaks and use <Property/> instead of <SystemProperty/>
jetty-https.xml that is includable as an app parameter

this adds an https connector in addition to the already defined HTTPConnector
remove rewrite handler example

there really is no sane use case for tricking Nexus into thinking it is using the https scheme when it isn't, except as a hack
make the http redirect to https configuration loadable as an app parameter

will require jetty-https.xml as well, but noted that in the comments
kitchen sink clean up

remove use of ${} style, adjust config to match latest jetty xml updates, add missing JMX gunk.

Remember this is an all-in-one config to get JMX, https redirect, and request logging using a single jmx file.
replace SystemProperty with property
Merge pull request #267 from sonatype/jetty-config-cleanup

NEXUS-6153 inline jetty config examples