![]() 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). The repositories that should initially be present in the application can be controlled using touchpoint instructions. The addRepository instruction should be used for each repository. In the p2 UI, we assume "colocated" metadata and artifact repositories. When the user adds a repository in the UI, both a metadata and an artifact repository are added for that location. When using touchpoint instructions, both the metadata and artifact repository must be added. These instructions can be specified using a touchpoint advice file (p2.inf) that is included with the application. Sample p2.inf file used in one of the p2 RCP Mail examples. 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). One workaround is to programmatically set the list of allowed repositories using.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |