Co-bundling Jetty ?

[Cantor, Scott]

On 9/12/13 1:00 PM, "David Langenberg" <davel at uchicago.edu> wrote:
>
>I don't see how you're going to get out of the support game for Jetty.
>If you list Jetty as the only container to which the project supports
>running the software, and I externally download it & have trouble you're
>gonna get a question on -users.

We get them now, and my answer is either a very quick "this is the answer"
or "go ask them". If other people choose to provide detailed container
help, that's welcome, but it isn't something I will do, not with the
amount of time I can afford to spend. But once we ship the container, we
can't take that position anymore. We own it all.

>You have the same problem today with Tomcat.  At the very least if you
>bundle in a specific Jetty version, that limits the scope of questions
>for configuring Jetty to just that version.

It won't though, because we're not going to stop supporting it as a stand
alone Java application running in any supported container, even if that
just means other Jetty versions. We'll still get all the questions
regardless.

>A comparison from another project I'm involved in -- Grouper. The grouper
> project ships a pre-configured Tomcat as part of our installer package.
>Now, I will grant that Grouper has a smaller install base than
>shibboleth, but even so, we rarely get any tomcat-specific questions on
>the -users list.

We get hundreds a year. Probably upwards of 10-15% of questions have
nothing to do with Shibboleth at all because people don't understand
Apache, IIS, Tomcat, whatever.

-- Scott