[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.tools.jdt] Re: Plugin Activation
|
"Leandro" <leandrop@xxxxxxxxxxx> wrote in message
news:eiom0d$378$1@xxxxxxxxxxxxxxxxxxxx
> Tanks Walter
>
> The two points in manifest.mf are ok.
> In this article
> http://www-128.ibm.com/developerworks/opensource/library/os-ecjdt/ the
> author said this:
>
> "Eclipse has a deferred load strategy to avoid loading plug-ins until the
> user does something that requires their code."
>
> In fact, when i put a "hello world" action button and click on this
> button, looks like the plugin is activated and them my debug message is
> printed. I read in some forum that, to put something in the initialization
> of the plugin i must use de extension point org.eclipse.ui.startup but all
> what i need is to know when my perspective button was fired. With the
> extension i get this working but i think it makes my plugin load everytime
> the Eclipse is openned, even when the perspective is not used. Am i right
> ?
>
> Tanks again !
That's correct: if you extend org.eclipse.ui.startup, then your plug-in will
be activated whenever Eclipse starts, which is usually a bad idea and almost
never necessary. The normal way to do things is to have Eclipse-LazyStart
set to true in the manifest; then the first time some UI action or call from
another plug-in causes your plug-in to need to be loaded, it will be loaded
and activated.