Community
Participate
Working Groups
In the new target API being worked on for 3.6, we are using p2's multiple agent api to store metadata, profile locations and more. Previously PDE stored it's p2 bundle cache and metadata in the workspace metadata folder. If we can move the agent data area outside of the workspace, all of the generated metadata and downloaded bundles could be made available to all workspaces. This would have significant performance improvements for anyone using multiple workspaces, especially for anyone creating their targets from remote repositories. We could make this agent area user configurable, but that may involve other issues. A reasonable place to put the agent area might be a sibling or child directory of the running Eclipse's p2 data area.
I'll be keeping this in mind when I work on using a p2 agent to manage the metadata.
I think the configuration area is the best candidate at the moment.
Maybe a Maven-like global repository (that could be used by any p2 product, not only by Eclipse itself) stored at a default location (like ~/.p2/) would be a long-sighted solution for this?
This is already possible with p2. I think for target management, we will default to the configuration area and leave it open for people to modify in the future. But yes, the goal is to have a shared repository.
