Community
Participate
Working Groups
My application (FlashBuilder) has a plugin xxx.1.0.1 in the plugins folder. I have dropped another product (set of plugins) into dropins folder - it also contains the same plugin but higher version - xxx.1.0.2 When FlashBuilder is launched, I can see through the bundles.info that Eclipse has loaded the higher version of xxx plugin from the dropins folder (xxx1.0.2). Now, after terminating the FlashBuilder, uninstall the newly installed product by manually deleting the set of plugins from dropins folder. Surprisingly during FlashBuilder re-start, my xxx.1.0.1 bundle from plugins folder is deleted by Eclipse/p2. I guess, the reason could be p2 garbage collects unreferenced plug-in when any un-installation/update activity happens. This would explain since the lower version of xxx bundle is no longer referenced. However, since the bundles comes from different products, I feel p2/Eclipse should not delete the bundles - as the un-installation of new product would remove the original bundle. My application is suffering major problem due to this issue. Can anyone atleast suggest a workaround in the meantime of fixing this problem ? This is the question raised at http://www.eclipse.org/forums/index.php?t=msg&goto=546860&#msg_546860
How did xxx.1.0.1 found its way in the installation in the first place? Given that this seems to be a complex setup, it would be great if you could provide a data set and steps on how to reproduce the problem with it.
Looks this problem is fixed with latest version of Eclipse (3.6).
