Re: [platform-core-dev] Imported optional plugins

[Debbie_Wilson@xxxxxxx]

The quick answer is 'it's intentional'.  But it's a good question so I'm taking the liberty of posting it to the newsgroup (as that's where this sort of thing is typically asked) and I'll post a more detailed response there.

                                                       Deb

Rod Iversen <riversen@xxxxxxxxxxxx> Sent by: platform-core-dev-admin@xxxxxxxxxxx 05/06/2002 03:12 PM Please respond to platform-core-dev

To:        platform-core-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-core-dev] Imported optional plugins

If an imported plugin is specified as optional in the plugin XML, the
versioning information seems to be ignored.
For example, given I have the following import statement in the plugin
requirements:

  <import plugin="com.alpha.beta" optional="true" version="2.0.0"
match="compatible"/>

If the version of the plugin com.alpha.beta is not compatible (e.g.
version 1.0.0), my plugin still loads without error.

I do expect my plugin to load, since the import is optional. However, I
also expect there to be a warning of the version mismatch generated in
the log. I would also expect that the imported plugin would not be made
visible in the namespace of my plugin, since it is of an incompatible
version. Eclipse currently does not conform to either of these
assumptions.

Is this intententional, or a defect?

Rod



_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev