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 ?
I forgot to say that my default auto-start is set to true and the "Auto-start" for all my plug-ins is set to default.
Anyway, I "fixed" the problem but I don't understand why it now works: what I did is simply remove the optional dependencies (unchecked the "Include optional dependencies when computing required plug-ins" and rebuilt the list of plug-ins). So, there is one optional plug-in that doesn't something preventing my plug-ins to start automatically.
I really checked that my plug-in didn't start by puttin a breakpoint at the beginning of the Activator (in case an exception was thrown in the start method) but the breakpoint is not reached.
Are you also using org.eclipse.equinox.simpleconfigurator? I think the issue is that old updateconfigurator does not handle the PDE settings for auto starting the bundles as specified in the launch configuration. You probably should open a bug against PDE->UI to investigate more.