Community
Participate
Working Groups
Build ID: Build id: M20080723-0800 Steps To Reproduce: As a product built on top of Eclipse and contain many components, we need all the components to be at a specific level to keep the integration of the product. To allow the components to update themselves may break the product. The Update Manager provides a nested feature structure and the top feature can control the update for all the children features. In the current P2, the repositories of all the components are exposed to the user. We need a way to hide the repositories of all the components and only expose the product repository. More information:
See also bug #234213.
Fixed >20081223 on the UI side, with the core part being handled during M4. See http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instructions for how a product can be configured to control the repositories. Summary: - you can set up your p2.inf file to use the touchpoint instruction addRepository for your repo - you can either use removeRepository to remove producer repositories, or alternately the metadata for your repository could simply omit any repository references from sites or IU's. See http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application#Restricting_Repository_Support for how to configure the UI so that no repository management features are shown in the UI.
Tried to the following on eclipse 3.5M6 without success. 1. Create a file p2.inf in the directory META-INF in my feature with the following content instructions.install = \ removeRepository (http://download.eclipse.org/datatools/updates,1);\ removeRepository (http://download.eclipse.org/datatools/updates,0); 2. Create an update site to build and host the feature 3. Install the feature in another instance of eclipse 3. Open the available software sites and the site http://download.eclipse.org/datatools/updates still exists. I also tried to put this file p2.inf in the directory META-INF of a plugin and it doesn't seem to work either.
I'm reopening the bug since it doesn't seem to work.
Samuel, I've created a clone bug (bug 269843) to discuss what you are trying to do, as this seems different than the original request. The touchpoint instructions are used at a product build level to set up the repository structure, whereas it sounds like you are trying to add a feature which would remove repos referenced by the product? Can we please move the discussion to the new bug, as this bug was tracking the ability to hide all site management features in the UI so that the user could not change what was configured at the product level.
Hi Susan, My request hasn't been changed. It stays the same as I opened this defect, which is to hide the repositories shipped in eclipse. I was trying to following what you suggested in comment #2, which is using the touchpoint to remove/add repository. If I misunderstood your instructions, please let me know what I should do. I'm reopening the bug. Thanks.
(In reply to comment #6) > Hi Susan, > My request hasn't been changed. It stays the same as I opened this defect, > which is to hide the repositories shipped in eclipse. > I was trying to following what you suggested in comment #2, which is using the > touchpoint to remove/add repository. If I misunderstood your instructions, > please let me know what I should do. > I'm reopening the bug. > Thanks. > I realize the request was multi-faceted. However, this bug covers "hiding" repos in the UI and is fixed. You won't get much further help with touchpoint issues in this bug. In order to best help you, I've moved the relevant new information to bug 269843, and you are already receiving suggestions/corrections to the syntax in that bug...
