[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.platform] How do I disable my own plugin at start up time?

Using 3.2:

In our plugin's start method we check that everything is there for it to work. For example certain native files must be there for the plugin to operate. In the case that something is missing, we want to plugin to be "disabled". That is, it is out of the user's way to do other things, but nothing with our plugin.

Currently, in the plugin's start method, if I see something is missing, I am throwing an exception. So, if the start method is called because someone chose our plugin's perspective, Eclipse says "problem opening perspective blah blah" and the perspective is not loaded.

My question is: Is throwing an exception in the start method the proper and only thing I have to do in this case?

by the way, checking for missing stuff is a lengthy operation for us, we have to lanuch a server, etc.