Eclipse update site layout

They are each a composite that simply points to the current version of the repositories listed below. Those using these non-versioned URL do not need to change their software repository lists or scripts.

In other words, the contents are identical to their current, versioned counterparts, but the URL stays the same. This page was last modified , 4 January by Sravan Kumar Lakkimsetti. Back to the top. The instructions describe the creation of an update site for the result of the basic tutorial: a modeling tool which simply allows the user to graphically represent a family.

If you followed the Sirius Starter Tutorial , you are ready! Directly go to next section: Create the Update Site. Otherwise, start by following the instructions to install the Basicfamily Domain Model and the solution of the Starter Tutorial. By default the icons defined in the modeler are not exported into the update site: you have to update the project definition in order to get these icons in the final modeler.

If you build an Eclipse application, you also create an update site. This can for example be done with Maven Tycho. For example, if you export it from the user interface you can select the Generate p2 repository option in the Eclipse product export dialog.

This option is highlighted in the following screenshot. If you select this option, an update site is created in a sub-folder called repository of the export directory. The following table lists the core plug-ins and the features, which provide the non-user interface functionality of p2. To use the Eclipse update API you need to include these plug-ins as dependencies to your manifest file.

And you must add the feature to your product configuration file. When the Eclipse installation is used as target platform, these required plugins should be already available. Otherwise they can be installed or added to a target definition file like this:.

If you place a p2. The following listing is an example for that. The Eclipse p2 functionality invokes actions touchpoints when an installable unit is installed, configured, or uninstalled. For example, it is possible to unzip or copy artifacts or to set file permissions.

The Eclipse p2 API uses install actions for this, called touchpoints. By default, it supports two touchpoint types, native and OSGi types.

Native touchpoint actions are not directly related to Eclipse such as file commands while the OSGi ones are Eclipse specific. It is possible to add custom touchpoint actions via the org.

The class which implements this touchpoint action must implement ProvisioningAction. It must also define how to invoke the execution of the custom touchpoint. It is possible to create p2 composite repositories.