Skip to main content

Equinox Incubator - Provisioning proposal


Eclipse has advanced quite quickly with new use-cases (RCP, Equinox, server side, etc.) and new technologies. However, to date Update Manager has not been enhanced to support or exploit these changes thus limiting the applications being developed.

Even though the 3.3 plan has items to overcome these limitations, no new work has been done due to time and resource constraints.

In order to ensure Update Manager receives appropriate attention in the next release of Eclipse, we are proposing the creation of a provisioning work area to develop new technologies and explore existing ones. The goal is for this work to graduate to be a replacement for Update Manager.

Scope of the proposal

In order to increase our chance of success, the scope of this incubator will be limited to the creation of a client-side provisioning framework that is functionally equivalent to the current Update Manager yet is more flexible and extensible.

The key characteristics researched by this work are:

  • sharing of plug-ins across multiple installations
  • configuration of non-running Eclipse and management of multiple configurations
  • separation of metadata and data to allow hosting on different servers (in Update Manager terminology, have site.xml on one server and the jars on another one)
  • integration with the OS prerequisites (e.g. JREs, registry entries, etc.)
  • support for the OSGi constructs
  • transactional operations (install, update, etc.)

Pluggability and flexibility goes without saying since it should be our underlying motto to enable things like pluggable transports, pluggable repositories (maven, OBR, etc.), flexible mirror choices, decision as to what to install / update, etc.


To ensure the suitability of the solution to a wide set of use cases, we are actively looking for interested parties (with or without technology) with definite interest in this area who are willing to contribute time and resources.


Given the foreseen impact of this work, we will have to operate under an aggressive schedule to be able to quickly produce a stable result. This will allow the platform team and interested parties ample time to review and buy in to this new provisioning story before integration into the Eclipse platform. If accepted, we intend to start integration of the new provisioning story as early as September 2007 and reach completion in December 2007, thus leaving us the rest of the release cycle for polish.


Please direct comments or questions to


Back to the top