![]() One workaround is to programmatically set the list of allowed repositories using .p2.ui. (source). If the RCP application will be installed into a user-write protected directory, p2.inf will fail to be able to add the repositories (as it tries to modify the configuration on the first RCP run). Sample p2.inf file used in one of the p2 RCP Mail examples. These instructions can be specified using a touchpoint advice file (p2.inf) that is included with the application. When using touchpoint instructions, both the metadata and artifact repository must be added. When the user adds a repository in the UI, both a metadata and an artifact repository are added for that location. In the p2 UI, we assume "colocated" metadata and artifact repositories. The addRepository instruction should be used for each repository. The repositories that should initially be present in the application can be controlled using touchpoint instructions. Configuring the user's default repositories This process is described in more detail in Andrew Niefer's blog post on the topic.Īn example build based on a modified RCP Mail application can be found here.Įnsure that you have the correct start levels and auto-start flags set for the bundles required to run the p2 processes (see this discussion). run the p2 director to provision the application.export the metadata for your build into a p2 repository.adding some p2-specific steps to the build.specifying the normal build steps in your build.properties.installing the delta pack for headless builds.It can also be done by expressing requirements in your features and letting the p2 install of your application pull in the right code. This can be expressed by including the p2 bundles in one of your product's features (using the feature 2.user.ui as a guide). The p2 bundles must be added to your application.The process for setting up your application to update with p2 involves several steps. 3.4 Modifying the p2 UI Policy while reusing the p2 UI featureĪdding p2, building, and provisioning your application with p2.3.3.2 Changing the Visibility of Available and Installed Content. ![]() 3.2 Reusing the Eclipse SDK UI without automatic updating. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |