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.
Difference between revisions of "Equinox/p2/Director application"
(→Terminology) |
|||
| Line 1: | Line 1: | ||
| − | The director application is a headless way of performing some of the p2 operations such as installing or uninstalling installable units. Given the appropriate metadata, this application is capable on provisioning a complete installation from scratch or simply extending your application. | + | The director application is a headless way of performing some of the p2 operations such as installing or uninstalling installable units. Given the appropriate metadata, this application is capable on provisioning a complete installation from scratch or simply extending your application. |
| + | |||
| + | Depending on the needs, this application can be executed inside or outside of the application being provisioned | ||
| + | |||
== Terminology == | == Terminology == | ||
Revision as of 11:26, 24 April 2008
The director application is a headless way of performing some of the p2 operations such as installing or uninstalling installable units. Given the appropriate metadata, this application is capable on provisioning a complete installation from scratch or simply extending your application.
Depending on the needs, this application can be executed inside or outside of the application being provisioned
Terminology
- Director application, the application performing p2 operations such as install or uninstall.
- Provisioning operation, an operation installing, uninstalling features.
- Target product, the installation targeted by the provisioning operation.
Provisioning from within the target application
It is contained in the org.eclipse.equinox.p2.director.app bundle. Provisioning from within inside In this case the provisioning operation happens from within the targeted produced that you are operating on. It is equivalent to starting up the target product and using the p2 UI to perform the equivalent operation. This means that the target application has to be in a runnable state and that it has to contain the the director application. The other drawback of this approach is that it will have caused the target application to have been run thus causing some cache files to have been created in the configuration folder (e.g. configuration/org.eclipse.osgi). This replaces the update manager command line application.
This example installs CDT into an eclipse platform. <command>