Why is my Plugin Activator not being started?

[KingAndrew]

Hi All,
I have an rcp. It has 2 plugins. One core and one ui. The activator for the ui is not getting called. The activator is:

Plugin extends AbstractUIPlugin
...
	public void start(BundleContext context) throws Exception {
		super.start(context);
		plugin = this;
	}

And in the MANIFEST.MF it has:

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Ui Plug-in
Bundle-SymbolicName: com.myco.omni.adminsuite.ui; singleton:=true
Bundle-Version: 1.0.0
[B]Bundle-Activator: com.myco.omni.adminsuite.ui.Plugin[/B]
Bundle-Vendor: myco
Require-Bundle: org.eclipse.ui,
 org.eclipse.ui.intro;bundle-version="3.2.201",
 org.eclipse.ui.console;bundle-version="3.3.0",
 org.eclipse.ui.forms;bundle-version="3.3.101",
 org.eclipse.ui.browser;bundle-version="3.2.201",
 org.eclipse.core.resources,
 org.eclipse.core.runtime,
 com.myco.omni.adminsuite;bundle-version="1.0.0"
Bundle-RequiredExecutionEnvironment: JavaSE-1.6

When I am in on of my Views I call Plugin.getDefault(); and it returns null so clearly the start method has not been called.

Does anyone see what I'm not doing that I should be?

Thanks in advance,

Andrew

[KingAndrew]

Talk about the weirdest thing. I still don't know why it wasn't calling/activating my plug-in so I decided to do it myself

Plugin plugin = Plugin.getDefault();
			if(null == plugin){
				plugin = [B]activatePlugin[/B](Plugin.PLUGIN_ID);
			}
...snip...

private Plugin [B]activatePlugin[/B](String pluginID) {
		Bundle bundle = Platform.getBundle(pluginID);
		try {
			bundle.start();
		} catch (BundleException e) {
			// Auto-generated catch block
			e.printStackTrace();
		}
		
		Application.writeToConsole("The Plug-in "+pluginID+" : "+bundle.getState());
		return Plugin.getDefault();
	}

So that got it to load my plug-in. Hurray!!

So I think I'll move that method somewhere that others can use it and while I'm trying it in the debugger from a fresh re-start of the application it does not get called but the start method on the plug-in is getting called like it should of from the start.

So it seems like the plug-in registry has learned that it is supposed to load that plug-in now.

Hope this helps someone else one day,

Andrew