Community
Participate
Working Groups
There are many issues and threads about plugins in dropins being ignored. While bug 264924 added p2 logging as an option, the amount of users having problems makes me wonder why logging is turned off by default. What is the downside? If a plugin is in dropins then obviously the user wants the plugin to be loaded and would always want to be informed why it was not loaded. Some threads and issues with debugging p2 dropins plugins: bug 345770 http://stackoverflow.com/questions/1489648/eclipse-doesnt-load-plugins-in-the-dropins-folder http://www-01.ibm.com/support/docview.wss?uid=swg21428463
Hi David, unfortunately dropins folder is a secondary installation mechanism, and it receives secondary support. The main issue with it is that plugins are loaded on the best-can-do basis. Of course some diagnosis would be welcome, there was even bug 174515, but I wouldn't count it will be implemented anytime soon (as it is against dropins "philosophy").
The best thing to hope for here is an exhaustive list of the plugins that have not been loaded. Getting an explanation as to why plugins have not been picked up would most likely take way too much time to compute to make it happen on startup. But as Krzysztof said, I would not put too much expectation on this to be fixed unless a patch was to be provided.
I know this is an old bug. Dropins were not supposed to log anything, but... droplets could: http://wiki.eclipse.org/Equinox/p2/Plan/3rd_party_installers
There is no resource to address issues such as this without the resource itself being contributed.
