Community
Participate
Working Groups
In a large installation, the "Installed Features" tab list becomes so large that it's easily unusable -- especially because it doesn't only display the installable "root features" but also some "child features" which cannot be uninstalled by themselves anyways. The tab should show the installed features as a tree rather than a list. I propose that 1. The root nodes of the tree should be the features' configured update sites (makes the view consistent to the "installable software" tab and provides an additional grouping similar to what's requested in bug 198941; 2. On the 2nd level, there should be the "root features" which are not themselves included in any other feature; below each "root feature", the included child features should be listed. "Conflicts", e.g. root feature from update site A but included child feature from update site B, the algorithm should first determine the full list of root features independent of update sites, and then group the root features by the update site specified within them (i.e. the update sites specified in any child feature are not considered at all). I also propose that the root nodes detected by this algorithm (i.e. the configured update sites detected from the root features) should be mapped to auto-generated group IU's as per bug 224145 comment 9. I further propose that in the absence of real extension locations, these auto-generated group IU's should be mapped to what an extension location was in the pre-P2 era, for the sake of grouping features in views such as the PDE Target Platform View (see bug 224145 comment 5, and bug 224145 comment 15). A dropdown control similar to the "Available Software" tab should allow switching back to the current presentation of features listed alphabetically, but the auto-generated group IU's should be available none the less. I'm marking this issue "major" because bug 224145 has been perceived as one of the major problems adopting P2, and I agree that finding the right feature(s) for (de)activation in the "installed software" tab or the "target platform" control is currently close to impossible in a large installation.
I'm marking this as a duplicate of bug #224472, and copied the specific suggestions over to that bug. One of the challenges in presenting the view you are requesting is that p2 is working with a more generic model underneath, so that the relationships between features and their sites is not currently modeled. This is obviously something we need to revisit based on feedback like yours. >especially because it doesn't only display the >installable "root features" but also some "child features" which cannot be >uninstalled by themselves anyways. This is most likely a bug/misunderstanding in the way p2 is used in the build process of the installation you are using. There is a specific way to mark install roots, and for a large installation, "child features" shouldn't be marked as roots. Once the SDK is running, only things the user chose to install get shown in this view, but what they see initially depends on how the build was configured. What installation are you referring to? For example, WTP has this issue in bug #232484. *** This bug has been marked as a duplicate of bug 224472 ***
