My guess is that we're currently not doing anything with the droplet features. I remember from working on http://pkgs.fedoraproject.org/cgit/rpms/eclipse.git/commit/?id=0199501365683a4827d38cd2ae21a4fa42bbdc78 that even in the TP we don't do anything with droplet features. If I get some time, I can probably put together a patch to fix this and upstream everything.
The InstalledSoftwarePage creates a viewer using InstalledIUGroup, and the input content is supplied by ProfileElement, which simply wraps the current p2 Profile within the profile registry. The p2 Profile will have listings for all bundles (which is likely why the plugins tab lists droplets), but the droplet solution as a whole doesn't add any features or feature groups to the profile. If we add this functionality it seems like the best way to do it is to extend ProfileElement to handle features from droplet locations and change the input element passed in by InstalledIUGroup to that new class.
Ok, so I've looked at this and need to revise some of my past statements. First of all, I can clearly see that p2 droplet provided features show up in the "Features" tab of "Installation Details". The p2 droplets code does check for features. The problem with respect to "Installed Software" is that the entries there are feature groups ($feature.feature.group). I like to think of these as an installable unit that wraps sets of features so that they actually show up in the p2 Installation Wizard. Our droplets don't check for these, and we don't even generate them. In the long term we would have to create some kind of dummy "${droplet} Droplet Group" (maybe through p2.inf or even in code at runtime) and ensure we add it to the profile to make it more clear that we've installed that thing through rpm.
Yet another update : Features only seem to show up after some bundle is installed onto the system (p2 has a chance to run) but plugins always show up.
This would appear to be a caching issue of some kind. Simple restarting the Eclipse instance (or shutting down and starting back up) displays the missing features. It appears that the feature data is cached and never refreshed.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Let's keep this open if something needs to be done -- Roland, please close if not :-)
Automation has figured out the package is retired in rawhide. If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement