Community
Participate
Working Groups
We should create a new preference scope that refers to the agent data area and we can store our repository preferences there.
This would be a good first step, however given that we want to store repos on a per profile basis we may need something else, or simply not use preferences to store this information. For example we had talked about storing the repos to be used in a "meta" profile.
*** Bug 213037 has been marked as a duplicate of this bug. ***
Do we even need this for 1.0? Sounds cool, but I can't think of a pressing use case that needs it.
It may not be necessary, but we need to find a way to set repositories when looking for updates in the end user ui, when the product has been laid down with the admin ui.
Here is what I have done: - There are two touchpoint actions (AddRepositoryAction and RemoveRepositoryAction) that can manipulate the set of repositories associated with a profile - These associated repositories are stored in the profile registry (in profile properties) - This set of associated repositories is only manipulated via engine operations as dictated by the metadata of some IU - When a profile is started, its associated repositories are "published" into the current configuration, and are stored in the configuration area as we have done in the past This distinguishes "built in" repositories that are added to a profile by some IU from other repositories that are added later by the user or some other plug-in. I'm not 100% sure on the direction but this has some interesting properties. For example this would allow recovery from a changed configuration location or lost configuration preferences. Publishing the associated repositories on startup is a bit of a hack. Ideally I would want all the logic for this hidden in the Eclipse touchpoint rather than have the profile registry aware of it. What is really needed here is a "finalize" phase where touchpoints can run some code after starting the newly provisioned profile. This would allow us to avoid adding this data in a profile property altogether.
