allow inlining jetty.xml config files as nexus app parameters

Nexus uses Jetty as it's container. Jetty can normally be configured by providing a list of jetty XML config files. These files are merged by jetty to form the final configuration.

It would be nice if the bootstrap code used by Nexus made use of this feature.

This has been implemented with

https://github.com/sonatype/nexus-oss/pull/245
https://github.com/sonatype/nexus-oss/pull/267

---- How it Works:

A user can enable this by adding an additional parameter to the wrapper.conf to load this configuration:

wrapper.app.parameter.1=./conf/jetty.xml
wrapper.app.parameter.2=./conf/jetty-requestlog.xml
# add more indexed app parameters...

When the server starts up, it will apply the configuration xml files (or load additional properties files) which are used to configure the Jetty server instance. This is based on the XmlConfiguration mechanism that standard Jetty uses:

Note: Request logging is now enabled by default with 90 day compressed log rotation using Logback.

All of the old examples have been updated to no longer be mere examples, but actual real inlinable jetty.xml files. For some a few additional properties may need setting. Comments are in each jetty file.