On Thu, Feb 21, 2008 at 4:20 PM, Alin Dreghiciu <[EMAIL PROTECTED]> wrote:
> 1. Create a copy of current pax web and change bundling process to not > embed jetty + add imports for jetty packages. This should solve Bret's > issue. This shouldn't be neccessary. Or are we saying that we want to claim to be the official maintainer of the Jetty Bundle? > 2. Pax Web will be build as a uber bundle containing artifact > mentioned above + necessary jetty artifacts + right import/export. > This will result in almost the same as the current bundle (+ > imports/exports fro jetty). So, if a new Jetty is released (and available in bundle form), deploy that bundle, stop Pax Web, refresh the bundles, start Pax Web, and it should be wired to the more recent version. Cheers Niclas _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
