[news.eclipse.technology.equinox] New states for plugins

["Pascal Rapicault" <pascal_rapicault@xxxxxxxxxx>]

In a different thread (classes for dynamix plugin events), Olivier was
surprised by some new state:
  disabled and primed.

Disabled has been the named that has always been used (since the first
version of the site) to indicate
a plugin whose functions are no longer available (see:
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/dynamic
Plugins/glossary.html and
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/dynamic
Plugins/registryLifeCycle.html)

The primed state of a plugin (defined in
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/dynamic
Plugins/registryLifeCycle.html) is a state where the plugin is not
"activated" but where some of its functions (not requiring the full power of
the plugin) can be made available. This is especially usefull for decorators
or filters (for example the binary project filter requires the all pde
plugin (and required plugins) to be activated just to NOT display
something...).

Olivier:
>While I am on the subject, I also don't quite understand
>the primed state... Does it mean that the class loader
>is present but the plugin has not executed any code yet?
>If so, this is very analog to the OSGi RESOLVED versus
>ACTIVE states for a bundle (remember a bundle is equivalent
>to a library plugin).

When a plugin is in a primed state: the plugin is not activated.
The classloader is here, classes can be loaded and instances created.
For more details on this see:
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/dynamic
Plugins/handlePrimedState.html

I don't think this is similar to the OSGi resolved status


Regards,

    PaScaL