Reconsider moving jetty-base out of idp-distribution ?

[Tom Zeller]

Moving a user thread [1] to dev, I'm wondering if we should reconsider
[2] moving jetty-base out of idp-distribution to somewhere else in the
Maven project stack/hierarchy. The reason to do so would be to "reduce
confusion", of course I'm not sure how effective making another change
will be in that regard.

I have not thought about it a lot, but a suggestion would be to move
jetty-base out of idp-distribution to a top-level java-idp-jetty
project. And I say top-level to indicate that it is not part of the
IdP proper. Parity would be a java-idp-tomcat project with
tomcat-base. A minor reason I suggest this is so that container
dependencies are in our stack to make it easier when uploading those
dependencies to Nexus, but that is not a big deal. Continuing the
thought, those top level container projects could be versioned
separately from the IdP according to the version of the container, to
keep *-base in sync.

I do not see a dependency on Jetty in the installer (idp-installer)
POM, but the testbed (java-idp-testbed) and integration tests
(java-idp-integration-tests) would need to look elsewhere for
jetty-base if we move it, obviously, but again that is not a big deal.

Just some thoughts.

[1] http://shibboleth.net/pipermail/users/2015-July/022765.html
[2] https://issues.shibboleth.net/jira/browse/IDP-639