Difference between revisions of "Equinox/p2/Removal"
Latest revision as of 16:58, 3 January 2011
Note: Although you are able to remove p2 from Eclipse SDK 3.4.x builds, it cannot be removed from 3.5.x builds due to increased integration with other components. In the 3.5 build cycle many components in the SDK have changed their dependencies to be on p2 and to call p2 API, rather than rely on the old Update Manager code, in preparation for removal of the Update Manager completely in a future release.
Eclipse platform Ganymede/3.4 contains two provisioning systems: the original Update Manager, and the new Equinox p2 provisioning platform. By default, p2 is in control of the system and the Update Manager is hidden. This page describes how to revert to the classic Update Manager and remove p2.
- Scripts available in bug 224908 automate this process (tested on Linux and Cygwin).
- For manual removal, the following should be deleted:
- Copy eclipse/configuration/config.ini from a 3.3.2 version of the platform into this release
- In the config.ini file, replace the "eclipse.buildId" setting with the correct build id (optional)
- Replace the eclipse/eclipse.ini file with the contents from Eclipse platform version 3.3.2.
Note an issue existed with removing the source plugins and features pre-3.4M7, see bug 228537.
Note that an issue was observed with I20080422-0800 and P2 removed, see bug 228546.