Community
Participate
Working Groups
Currently, when adding a software site to a target platform, the list of update sites only includes sites that are being worked with for the target platform. There is typically a lot of overlap between runtime environment and target platform. But currently if you want to use a site that is already added to your runtime environment, you have to close out of the target platform window, got to your environment install, copy the URL return to the target platform.. It would be great to have the environment's list of update sites available directly from within the target platform software site dialog.
The separation between the two lists was done on purpose. Before they were separated, changes to one would cause odd behaviour in the other. Furthermore, always adding the runtime sites to the target list will pollute it rapidly. Maybe having a separator in the list and just importing those that aren't dupes could work, but I do not have time to investigate. I feel that this bug is unlikely to get fixed and should be closed as WONTFIX.
I thought it might have been, and I can see the issues with having them separate. What about an "Import from environment" hotlink or something? I'm not suggesting that this be a high-priority item, perhaps it could be set as "help-wanted" or something.
A little off topic, but what about being able to copy the _currently used_ update sites (that is, those that have features installed from them) and ideally their feature choices from the current environment. I realize the second part of that is problematic, since you won't have a base platform for site based resolution but even if we just included the current eclipse_home as well.
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
