Eclipse Community Forums: Equinox » Relation between plugin activation and enabling/disabling Eclipse Feature

Home » Eclipse Projects » Equinox » Relation between plugin activation and enabling/disabling Eclipse Feature

Relation between plugin activation and enabling/disabling Eclipse Feature [message #107944]

Fri, 11 April 2008 02:30

Eclipse User

Hi All,

What is the impact of enabling/disabling an Eclipse Feature version (through Help-->Software Updates-->Manage Configuration) on activation/deactivation/installation of plugins referenced by such a Feature?

e.g. Feature F1 version 1.0.0 references Plugin P1 version 1.0.0 and Feature F1 version 2.0.0 references Plugin P1 version 2.0.0. If F1 version 2.0.0 is disabled, F1 version 1.0.0 enabled, and a class from Plugin P1 is loaded, this class is loaded from P1 version 1.0.0.

How is it that plugin versions referenced by a Feature version that is disabled are not considered when plugin activation takes place?

Any pointers in understanding this would be most appreciated.

TIA,
Kind Regards,
-abhi

Re: Relation between plugin activation and enabling/disabling Eclipse Feature [message #108016 is a reply to message #107944]

Sun, 13 April 2008 16:22

Eclipse User

Originally posted by: manahan.NOSPAM.ca.ibm.com

org.eclipse.update.configurator is listed in the config.ini as a startup
bundle. This bundle determines which bundles (aka plugins) contributed
by Update Manager (i.e via features, sites, extension directories etc)
should be passed to the runtime. Each feature contains an explicit list
of bundles. The features that are active are read and the list of the
bundles they contain passed to the runtime. Features which are inactive
do not have their bundles passed to the runtime.

So in the case you describe Feature 1.0 is active and therefore eclipse
knows about Plugin 1.0 and doesn't know about Plugin 2.0 so it loads
1.0. Plugin 2.0 was basically filtered out.

So while features don't define how the eclipse runtime loads bundles
they can define which bundles the eclipse runtime knows about.

P2 may change all this since it will replace update manager eventually.

-Peter
abhi wrote:
> Hi All,
>
> What is the impact of enabling/disabling an Eclipse Feature version (through Help-->Software Updates-->Manage Configuration) on activation/deactivation/installation of plugins referenced by such a Feature?
>
> e.g. Feature F1 version 1.0.0 references Plugin P1 version 1.0.0 and Feature F1 version 2.0.0 references Plugin P1 version 2.0.0. If F1 version 2.0.0 is disabled, F1 version 1.0.0 enabled, and a class from Plugin P1 is loaded, this class is loaded from P1 version 1.0.0.
>
> How is it that plugin versions referenced by a Feature version that is disabled are not considered when plugin activation takes place?
>
> Any pointers in understanding this would be most appreciated.
>
> TIA,
> Kind Regards,
> -abhi

Re: Relation between plugin activation and enabling/disabling Eclipse [message #108349 is a reply to message #108016]

Thu, 17 April 2008 10:06

Eclipse User

Hello Peter,

Thanks a lot for your input. In addition to clarifying the doubt, you have opened another avenue for me to explore (Eclipse P2).

Thanks a lot!

Best Regards,
-abhi

Previous Topic:	NPE in my Servlet init kills http registry service...
Next Topic:	P2 profile creation problem

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 11:01:26 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter