|Forcing a plug-in to start [message #667337]
||Thu, 28 April 2011 04:35
| Cedric Moonen
Registered: August 2009
I developped an RCP application (with a product definition) with Eclipse Galileo and everything worked fine.
I now updated to Helios and the way plug-ins are started has apparently changed. Now, my different plug-ins do not start automatically anymore.
Some of my plug-ins are started correctly because they are set to lazy start ("Activate this plug-in when one of its classes is loaded" is checked) and some other plug-in will use one of the classes of this plug-in.
But there is one plug-in that is not started anymore (because no other plug-in loads one of its classes). I disabled the auto-start but it doesn't fix the problem: my bundle is still in the "Resolved" state. This plug-in doesn't add contribution to the UI (so it doesn't have a plugin.xml file), if that makes a difference.
Is there a way I can force a plug-in to start ?
What is the difference between Ganymede and Helios on the startup sequence ?
Powered by FUDForum
. Page generated in 0.01571 seconds