Difference between revisions of "Equinox/p2/Director application"

From Eclipsepedia

< Equinox‎ | p2
Jump to: navigation, search
 
(47 intermediate revisions by 13 users not shown)
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 [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html 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 of provisioning a complete installation from scratch or simply extending your application.  
  
== Terminology ==
+
Depending on the needs, this application can be executed inside or outside of the application being provisioned. For complete documentation on the director, including a full list of supported arguments and related examples, see the official [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html p2 director documentation].
* 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.
+
+
  
It is contained in the org.eclipse.equinox.p2.director.app bundle.
+
== Scripted Examples ==
Provisioning from within inside
+
* [[Equinox_p2_director_application/Examples/Install_into_dropins|Install into eclipse/dropins/]]
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.
+
* [[Equinox_p2_director_application/Examples/Install_into_dropins_with_link_file|Install into eclipse/dropins/ with .link file]]
This means that the target application has to be in a runnable state and that it has to contain the the director application.
+
* [[Equinox_p2_director_application/Examples/Install_into_eclipse_using_SDKProfile|Install into eclipse/ using SDKProfile]] (the [[Equinox_p2_Update_UI_Users_Guide|p2 Update UI]]'s default behaviour)
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>
+
  
 +
== See Also ==
  
[[Category:Equinox_p2|Director application]]
+
* [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html Installing software using the p2 director application]
 +
 
 +
[[Category:Equinox_p2|Director application]] [[Category:Equinox_p2_Director]]

Latest revision as of 08:03, 29 June 2011

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 of 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. For complete documentation on the director, including a full list of supported arguments and related examples, see the official p2 director documentation.

[edit] Scripted Examples

[edit] See Also