Community
Participate
Working Groups
There are a number of Eclipse projects and products that are making use of equinox on the server through the servletbridge. The changes we're introducing in p2 will very likely have an impact on the deployment of these applications. We can probably still use update.configurator in the old way for these applications, but either way we should perform some validation in this area.
*** Bug 223255 has been marked as a duplicate of this bug. ***
Re-iterating that we are not planning on doing p2 work for the server for the 3.4 release. There's no reason why it shouldn't just work however we're unlikely to specific targetted work here. I'll do some validation post m7 to ensure that the use of update configurator in this environment is still fine.
A product team ran into a situation where they were launching the Servletbridge inside the IDE using Jetty directly. The update.configurator failed to reconcile because p2 sets the System property "org.eclipse.update.reconcile" to "false" which prevents automatic reconciliation with plugins/ and features/. The workaround was to set this property "true" and then later reset it after the servletbridge framework instance was up and running. I'll open a separate bug to look at update.configurator accessing this property as a BundleContext property instead but wanted to note the workaround in case others run into this problem.
Simon and Scott have done an awesome job of providing a solution for this in 3.6 (org.eclipse.equinox.server.p2).
