3.1.2 -> 3.2.0 where art thou jetty-base?

[Chris Phillips]

Thanks Scott and Rod..

I have a better view on the structure through the responses and see where
things are going -- abstracting out the container configuration and to be
'downstream'.
In essence, that's the style of activity we're doing with the our
installer work and the enhancements in the v3.x installation process have
been really helpful.

My original question has been answered for 3.2.0 and see a glimpse of
what's coming for 3.next after this one.

FWIW, I do see a high degree of value for a reference configuration of the
chosen container.  Ease of deployment and effort to upgrade/sustain has
frequently been the complaint for sites to adopt Shibboleth as a
component.  In the sustaining front, kudos on the v3 work regarding the
overlay technique -- that's a big gain too.

Given that Shibboleth has chosen Jetty as the primary one I would suggest
that a 'reference jetty-base' exist somewhere beyond just written
documentation that can be referenced or easily cloned for a given version
of Shibboleth.  While I know you've said 'don't depend on it' it has
nonetheless been very helpful to bootstrap jetty installs as well as
continuous integration testing of the IdP that we do and suspect the Shib
dev team does with Jenkins.


C


On 2015-11-23, 6:06 AM, "users on behalf of Rod Widdowson"
<users-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

>> We never shipped it for public use. That is our content for our purposes
>and has
>> no relevance to what anybody else does. Do not depend on it in any way.
>
>I'll add (as fair warning) that current plans are for this folder to go
>away
>in the next functional release.  Jetty has nothing to do with the IdP, and
>we will be moving this technology (and hence the windows installer) down
>stream of the IdP.
>
>Rod
>
>-- 
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net