Reconsider moving jetty-base out of idp-distribution ?

[Rod Widdowson]

> Restating what I am wanting : (1) to make sure we version jetty-base
> and jetty.version (in the POM) together properly, and less importantly
> (2) include jetty-distribution as a dependency in the stack (in order
> to manage dependencies in Nexus).

Right.  I was half playing with an idea for a "deployable jetty" project
which collects jetty from Maven and bundles it up with our jetty base.  If
we could use that in the windows installer and we could use it for the
testbed and the integration tests.  We could use the standard install
techniques to make that all *just* work.

Best of all it would remove the bifurcation of how we get hold of jetty and
make sure that we really have shipped what we tested.
 
> Right now, bumping jetty.version in the parent POM means we bump
> everything (I think), so I am wondering if we need to move
> jetty.version down in the POM hierarchy. For example, if we need to
> respond quickly to a Jetty fix.

That too.

But by point is that this is not a small change.  What we have works (more
or less) and we need some not insignificant design to make sure it hits all
the hot spots.

Rod