Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Equinox p2 Plan
As we have seen during the provisioning workshop, the problematic of provisioning can be quite broad. In order help us make focused progress, we will first be working on install / update / uninstall of plug-ins since one of our goal is to replace the current update manager. The other focus will be on trying to use our own technology as soon as possible (a.k.a "dog"-fooding).
Scenario title
Install/Update/Uninstall software from eclipse obtained from an SDK archive Scenario description: The user gets eclipse by downloading an archive of the SDK. It unzips it and run it. It goes to the update manager UI and decides to install / update / uninstall plug-ins.
Simplifying assumptions
The "agent" is part of the downloaded SDK and it will be running in process. The plugins folder of the install is the plug-in pool. Metadata and artifact repositories are delivered as part of the archive. All agent data necessary to represent the eclipse installed by the SDK is delivered as part of the archive.
Tasks
- Define and implement the concept of groups - Define and implement a mechanism to filter the content of a group
- Implement support to have remote metadata and artifact repositories
- Implement uninstall in the director - Implement the uninstall operation for the engine - Metadata for uninstallation of eclipse (format and generation) - Implement uninstall in the eclipse touchpoint
- Implement update in the director 3d - Implement unconfigure in the eclipse touchpoint
- Implement the garbage collector from the repositories
- Ability to write into repositories
- Ability to remove a plug-in from the bundle pool - Ability to remove metadata from the metadata cache
- Generation of groups from features 1d
- Mechanism to ship the install registry, artifact reg, etc. as part of the SDK 2d