Jetty configuration roundup for v3

[Cantor, Scott]

> By "embedded" I mean configuring Jetty in Java, and I do not think
> this will be flexible enough for deployers. It also means we would
> need to provide our own start|stop scripts, instead of leveraging
> Jetty's.

I think that's a given with shipping this with a container, though. It's not meant to be flexible, quite the opposite. It should be targeted at a specific configuration and anything else is "do it yourself".

I can't really imagine the idea of not doing it myelf, using something I don't control would be horrifying to me. But that was the idea, I think.

> Finally, I am interested in Jetty's new start.d modular start style. I
> am hoping we can simply provide a 700-shib.ini file, which will still
> allow deployers to turn on setuid or whatever they need.[1] There is a
> recent jetty-dev thread where we can provide feedback if we need to.

Not familiar with it.

-- Scott