Co-bundling Jetty Part II

[Tom Zeller]

The comments I have received have been really helpful and I have a
very initial proposal for what-to-do-about-Jetty. More comments, as
always, are welcome.

Basically, I propose changing "-" to "/". Meaning, change the
installation directory from /opt/shibboleth-idp to
/opt/shibboleth/idp.

Make the installer a top level "product" like the IdP and MDA (or is
that MA ?). Pull the installer out of the IdP and bump it up a level,
as peer of shibboleth/idp, but just port the Ant script from v2 making
minimal changes to paths, which should be straightforward. Consider
modifying the installer to install the MDA.

Decouple Jetty and IdPv3 versions by pulling Jetty out of IdPv3 and
bump it up a level to shibboleth/jetty, and tie the Jetty version to
the Installer version. So remove Jetty as a dependency of the IdP. If
folks want to use it, great, if not, the IdP does not change.

Hand-wave about extensions, let them live as peers of the Installer,
IdP, and MDA in an extensions/ directory, and think about how the
Installer might peruse that directory.

If the Installer can install v3, let it install v2 as well and
consider a v2 to v3 Upgrader which might benefit from a common layout
between versions. If v2 and v3 live inside /opt/shibboleth, maybe they
should be /opt/shibboleth/idp[23]. Consider a 2.x release where the
only change is the installation paradigm, hopefully making the path to
v3 easier.

The idea is fairly lazy, port what we have already, but re-organize
for the future. The stuff at the end is the most optional.