Community
Participate
Working Groups
As more enhancements are added to the target platform, some users are finding a need to have more control over the inner workings of the target. This is especially true when working with p2 as a large number of repositories, directories and other information is involved with the user having no way to see (or edit) it. Adding additional options to the current target platform page is not very practical, as many options only relate to p2 targets. There is also a few target options on the main PDE preference page, but there isn't much room left on that page. However, I think we should start by adding a new section to the main page called "Advanced Target Platform Settings". 1) Manual garbage collect option 2) Location of the PDE bundle pool (read only for now) Less important: 3) Option to only check remote repositories (from bug 327668) 4) Ability to add additional artifact repositories
FWIW I'm fine with a separate page. not sure if it is "Advanced" or something more p2 specific. The options there (so far) are all p2 or Software Site related. 1) +1 2) I'm not sure we want people to mess with the location of the bundle pool. It could be interesting BUT there are issues iwth concurrent access to the simple artifact repos that are used. People setting the value the same in two different Eclipses run the risk of corruption or failures. For now we would likely do well to keep the actual bundlepool hidden. 3) This is IMHO an important safety valve. If for some reason things get screwed up, the solution is to check the "Use only specified repos" option. This could be phrased as a global option though the facilities are in the patch to do finer granularity. 4) The most likely candidates here are other workspaces. Perhaps "related workspaces". Other Eclipse installs (IDE or otherwise) may also be interesting. Right now I grovel UI prefs for related workspaces and use the current IDE. Random directories / zips of artifact repos might also be interesting. This one feels like a bit more work to get the lifecycle and management right.
(In reply to comment #1) > 2) I'm not sure we want people to mess with the location of the bundle pool. I think the underlying use case is to have a system bundle pool where all atrifacts are stored so that one doesn't have to download things again in a different workspace. Something like Maven does by storing artifacts in the user's home directory.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
